From 319dfdb87da3ba8d4c37a881c58f4061637c02b8 Mon Sep 17 00:00:00 2001 From: Tiago Pascoal Date: Thu, 8 Oct 2020 12:46:59 +0100 Subject: [PATCH] fix some ghcr docker call examples had a typo when specifing image tag --- .../pushing-and-pulling-docker-images.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md index f278fee455bb..e4e1db91970c 100644 --- a/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ b/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md @@ -20,7 +20,7 @@ To push and pull container images owned by an organization, an organization admi This example pushes the latest version of `IMAGE-NAME`. ```shell - $ docker push ghcr.io/OWNER/IMAGE_NAME.latest + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest ``` This example pushes the `2.5` version of the image. @@ -42,7 +42,7 @@ To ensure you're always using the same image, you can specify the exact containe ``` 2. Remove image locally as needed. ```shell - $ docker rmi ghcr.io/OWNER/IMAGE_NAME.latest + $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest ``` 3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.