Docker image pull

KodeKloud Engineer
#1

hi,

I have pull the docker image and re-tag it. why it shows failed?

mage busybox:musl is not pulled on Application Server 3

here is what i did:

root@stapp03 banner]# docker pull busybox:musl
musl: Pulling from library/busybox
b1911a451216: Pull complete
Digest: sha256:f61fd8b11fc8b32e432f2434dae1231ccecee65ece7803d7216b3d43ea871c6d
Status: Downloaded newer image for busybox:musl
docker.io/library/busybox:musl
[root@stapp03 banner]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox musl 4bddb727aebd 4 weeks ago 1.47MB
[root@stapp03 banner]# dokcer tag busybox:musl busybox:media
bash: dokcer: command not found
[root@stapp03 banner]# docker tag busybox:musl busybox:media
[root@stapp03 banner]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox media 4bddb727aebd 4 weeks ago 1.47MB
busybox musl 4bddb727aebd 4 weeks ago 1.47MB
[root@stapp03 banner]# docker rmi busybox:musl
Untagged: busybox:musl
[root@stapp03 banner]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox media 4bddb727aebd 4 weeks ago 1.47MB

#2

I think you should not delete the old image (busybox:musl) , I believe it is not mentioned in question to delete the old image.

#3

The question says to “re-tag” it, it should meant like re-name it, so imply to delete the old image. Maybe question should be more clearly stating not to delete the old copy, or saying create another tag for it? Would you mark this as success for me? thanks. -jenna :wink:

#4

@kodekloud-support3
I have made the same mistake, I retaged the image and then deleted the old tag so that only one tag is left. The question is not clear enough. It is nowhere mentioned that the old image needs to be left alone. Can you mark as success for me also?