## Push the image
Let's try to push the image to Docker Hub.
1. In the command line, run the following commmand:
```console
docker push docker/getting-started
```
You'll see an error like this:
```console
$ docker push docker/getting-started
The push refers to repository [docker.io/docker/getting-started]
An image does not exist locally with the tag: docker/getting-started
```
This failure is expected because the image isn't tagged correctly yet.
Docker is looking for an image name `docker/getting started`, but your
local image is still named `getting-started`.
You can confirm this by running:
```console
docker image ls
```
2. To fix this, first sign in to Docker Hub using your Docker ID: `docker login YOUR-USER-NAME`.
3. Use the `docker tag` command to give the `getting-started` image a new name. Replace `YOUR-USER-NAME` with your Docker ID.
```console
$ docker tag getting-started YOUR-USER-NAME/getting-started
```
4. Now run the `docker push` command again. If you're copying the value from
Docker Hub, you can drop the `tagname` part, as you didn't add a tag to the
image name. If you don't specify a tag, Docker uses a tag called `latest`.
```console
$ docker push YOUR-USER-NAME/getting-started
```
## Run the image on a new instance
Now that your image has been built and pushed into a registry, try running your app on a brand
new instance that has never seen this container image. To do this, you will use Play with Docker.
> [!NOTE]
>
> Play with Docker uses the amd64 platform. If you are using an ARM based Mac with Apple silicon, you will need to rebuild the image to be compatible with Play with Docker and push the new image to your repository.
>
> To build an image for the amd64 platform, use the `--platform` flag.
> ```console
> $ docker build --platform linux/amd64 -t YOUR-USER-NAME/getting-started .
> ```
>
> Docker buildx also supports building multi-platform images. To learn more, see [Multi-platform images](/manuals/build/building/multi-platform.md).