Hide Forgot
Description of problem: > # docker images |grep busybox.*latest (nothing) > # docker inspect -f '{{.Id}}' centos:latest > sha256:97063303644439d9cea259b0e5f4b468633c90d88bf526acc67e5ae0a6e9427c > # docker tag centos:latest busybox:latest > # docker inspect -f '{{.Id}}' busybox:latest > sha256:97063303644439d9cea259b0e5f4b468633c90d88bf526acc67e5ae0a6e9427c As expected, busybox:latest is set to this not-busybox image > # docker pull busybox:latest > Trying to pull repository docker.io/library/busybox ... > latest: Pulling from docker.io/library/busybox > 56bec22e3559: Pull complete > Digest: sha256:29f5d56d12684887bdfa50dcd29fc31eea4aaf4ad3bec43daf19026a7ce69912 > Status: Downloaded newer image for docker.io/busybox:latest BUT: > # docker inspect -f '{{.Id}}' busybox:latest > sha256:97063303644439d9cea259b0e5f4b468633c90d88bf526acc67e5ae0a6e9427c the very same image I wanted to pull is not updated, it still points to the CentOS image! This is because the (docker pull) has instead updated > # docker inspect -f '{{.Id}}' docker.io/busybox:latest sha256:e02e811dd08fd49e7f6032625495118e63f597eb150403d02e3238af1df240ba Version-Release number of selected component (if applicable): docker-1.10.3-54.gite03ddb8.fc24.x86_64 , but this presumably applies to most branches of projectatomic/docker with the --add-registry patch Expected results: I _think_ that (docker tag), (docker load) and anything else which tags images should turn unqualified references (= references without a host name) into references qualified with the default repository (or always with docker.io?). See https://github.com/containers/image/issues/72 for a much more detailed analysis. OTOH, looking at #1255077 , #1241950 , #1198838, this is a tricky area and perhaps this has been tried and abandoned in the past.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Same in docker-1.13.1-51.git4032bd5.fc28.x86_64 .
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Wame in docker-1.13.1-65.git1185cfd.fc28.x86_64, per %changelog this is likely to exist in F30 as well.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.