Menu
I tried to pull the Fedora docker image using the following command but it failed with Tag latest not found in repository docker.io/library/fedora error:
# docker pull fedora
Using default tag: latest
latest: Pulling from library/fedora
62b0615068df: Pull complete
cd1e9127a3f8: Verifying Checksum
Pulling repository docker.io/library/fedora
Tag latest not found in repository docker.io/library/fedora
However, it succeeded when I pulled it with the latest tag explicitly specified.
docker pull fedora:latest
latest: Pulling from library/fedora
cd1e9127a3f8: Pull complete
Digest: sha256:52db7a1a18f173622a9b1a75354c7266220bffb7187c4880590805af0d7679d6
Status: Downloaded newer image for fedora:latest
In an attempt to understand this further, I tried to pull the CentOS docker image. However, I did not see this behavior in case of CentOS:
docker pull centos
Using default tag: latest
latest: Pulling from library/centos
Digest: sha256:1a62cd7c773dd5c6cf08e2e28596f6fcc99bd97e38c9b324163e0da90ed27562
Status: Downloaded newer image for centos:latest
Version Info
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)
# docker -v
Docker version 1.9.1, build a34a1d5
Can someone please help me understand this behavior?
588
By default, Docker pulls the latest version. To ensure it does so, you can add the :latest tag.
The latest tag is applied to the most recent docker build or docker tag command that was run without a tag value explicitly set. Therefore, it's possible to run docker commands out of order or to explicitly set tags on some images. Both scenarios cause the latest tag to refer to a build that isn't the most recent.
Using docker run to get the image We could have skipped the docker pull step; if you use the docker run command and you don't already have a copy of the Docker image, Docker will automatically pull the image first and then run it.
Looks like Docker is handling network errors in a wrong way. E.g. DNS timeout may be reported as "Tag xxx not found". That's why an error may be intermittent. Saw that few times, changing DNS server to google DNS (8.8.8.8) and waiting for few minutes fixed this docker error for me.
109
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
