Bug 1507679

Summary: Docker default registry change breaks many default behaviors including docker.com tutorial
Product: [Fedora] Fedora Reporter: DaveC <laidbackdave_nc>
Component: dockerAssignee: Frantisek Kluknavsky <fkluknav>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: adimania, admiller, amurdaca, dwalsh, fkluknav, ichavero, jcajka, lsm5, marianne, nalin, santiago, vbatts
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: docker-1.13.1-40.git877b6df.fc26 docker-1.13.1-42.git4402c09.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-25 02:35:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description DaveC 2017-10-30 22:07:06 UTC 
Description of problem:
As a new user of docker going through the docker.com tutorial, many things do not work as expected using the fedora v26 docker package.  Be stealing the default registry from docker.io and silently changing the registry default, simple commands like "docker login" now have undocumented and silently changed meanings.
This means that you are logging in to the wrong registry with your docker.io credentials that say they are successful.  Then when trying to push to a docker.io registry entry, it fails because you haven't logged in.  Then when you finally figure out that your private docker registry being referenced, you have to figure out to re-login with an explicit reference to docker.io that is not documented anywhere (nor does it work that way on any other docker platform).

So pushing images to docker.io registry doesn't work as documented on docker.com and is not in the Fedora 26 release notes either!!
Docker users should stay away from Fedora docker as it also means that downloading public "official" images are now coming from a fedora registry and not the expected docker.io registry.

Adding an additional Fedora registry might be fine but replacing the docker "official" registry is a very nasty trojan horse where unsuspecting docker users are not getting what they expect (and in some cases badly out of date images).

I saw where this "feature" was consider to have only "isolated impact".  You seriously need some architectural review of features like changing package defaults when they are industry wide multiple platform technologies.  I hate to think what you might do to Kubernetes or OpenStack.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.install docker
2. docker login
3. docker push public-docker-registry/image:tag

Actual results:
push fails -- not authorized to push to fedora registry!!!

Expected results:
image pushed to your docker.io registry

Additional info:
Never change defaults like registries of multi-platform technologies
Comment 1 Fedora Update System 2017-11-02 19:16:31 UTC 
atomic-1.19.1-5.fc27 docker-1.13.1-37.git166a52e.fc27 skopeo-0.1.24-6.dev.git28d4e08.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 2 Fedora Update System 2017-11-02 19:17:19 UTC 
atomic-1.19.1-5.fc27 docker-1.13.1-37.git166a52e.fc27 skopeo-0.1.24-6.dev.git28d4e08.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 3 Fedora Update System 2017-11-02 19:46:05 UTC 
atomic-1.19.1-5.fc26 docker-1.13.1-37.git166a52e.fc26 skopeo-0.1.24-7.gitdd2c3e3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cbf83e5281
Comment 4 Fedora Update System 2017-11-03 14:22:47 UTC 
atomic-1.19.1-5.fc26, docker-1.13.1-38.git166a52e.fc26, skopeo-0.1.24-7.gitdd2c3e3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cbf83e5281
Comment 5 Fedora Update System 2017-11-03 19:49:30 UTC 
atomic-1.19.1-6.fc26 docker-1.13.1-40.git877b6df.fc26 skopeo-0.1.24-7.gitdd2c3e3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cbf83e5281
Comment 6 Fedora Update System 2017-11-04 18:00:48 UTC 
atomic-1.19.1-5.fc27, docker-1.13.1-38.git166a52e.fc27, skopeo-0.1.24-6.dev.git28d4e08.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 7 Fedora Update System 2017-11-04 19:56:56 UTC 
atomic-1.19.1-6.fc26, docker-1.13.1-40.git877b6df.fc26, skopeo-0.1.24-7.gitdd2c3e3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cbf83e5281
Comment 8 Fedora Update System 2017-11-06 19:01:57 UTC 
atomic-1.19.1-6.fc27 docker-1.13.1-40.git877b6df.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 9 Fedora Update System 2017-11-06 21:13:51 UTC 
atomic-1.19.1-6.fc27, docker-1.13.1-40.git877b6df.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 10 Fedora Update System 2017-11-12 22:13:21 UTC 
docker-1.13.1-41.git0861eff.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 11 Fedora Update System 2017-11-14 10:56:15 UTC 
docker-1.13.1-41.git0861eff.fc27, skopeo-0.1.25-2.git7fd6f66.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 12 Fedora Update System 2017-11-15 20:09:16 UTC 
atomic-1.19.1-6.fc26, docker-1.13.1-40.git877b6df.fc26, skopeo-0.1.24-7.gitdd2c3e3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Comment 13 Fedora Update System 2017-11-17 16:23:07 UTC 
docker-1.13.1-42.git4402c09.fc27 skopeo-0.1.25-2.git7fd6f66.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 14 Fedora Update System 2017-11-18 00:53:50 UTC 
docker-1.13.1-42.git4402c09.fc27, skopeo-0.1.25-2.git7fd6f66.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3da8ad596a
Comment 15 Fedora Update System 2017-11-25 02:35:16 UTC 
docker-1.13.1-42.git4402c09.fc27, skopeo-0.1.25-2.git7fd6f66.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.