Description of problem: This is what's written in the docker-login man page: ... snip ... Log in to a Docker Registry located on the specified SERVER. You can specify a URL or a hostname for the SERVER value. If you do not specify a SERVER, the command uses Docker's public registry located at https://registry-1.docker.io/ by default. To get a username/password for Docker's public registry, create an account on Docker Hub. ... snip ... However, running 'sudo docker login' actually logs into https://registry.fedoraproject.org/v1/. Version-Release number of selected component (if applicable): docker-1.13.1-19.git27e468e.fc26.x86_64 How reproducible: Always. Steps to Reproduce: [tadej@toronto ~]$ sudo docker login Username: tjanez Password: Login Succeeded Actual results: [tadej@toronto ~]$ sudo cat /root/.docker/config.json { "auths": { "https://registry.fedoraproject.org/v1/": { "auth": "... removed ..." } } } Expected results: Either 'sudo docker login' would login to Docker's public registry, i.e. https://index.docker.io/v1/, or the documentation is changed and users are instructed that they must use 'sudo docker login docker.io' to login to Docker's public registry.
documentation needs to be fixed as docker login tries to login to the first "--add-registry" flag (which, if no flag is provided defaults to docker.io).
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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.