Bug 1420279

can you please provide commands to reproduce this along with expected and current behavior? The docker login goes to whatever default registry you have configured with --add-registry in /etc/sysconfig/docker so apart from that misleading output about docker ID, a docker login should behave like that with projectatomic/docker.

How reproducible:
1. system without docker
2. yum install docker-1.10.3-59.el7 && systemctl start docker
3. docker login docker.io (with your Docker Hub credentials) 
  In .docker/config.json there is:
{
	"auths": {
		"https://index.docker.io/v1/": {
			"auth": "xxxxxxxxxx",
			"email": "mskalick"
		}
	}
}

4. Now it is possible to push to personal namespace in Docker Hub
5. yum install docker-1.12.5-14.el7
6. Now it is NOT possible to push to personal namespace in Docker Hub (unauthorized: authentication required; .docker/config.json is the same)

Continues how it works for me:
7. docker login (with your Docker Hub credentials)
  In .docker/config.json there is:
{
	"auths": {
		"https://index.docker.io/v1/": {
			"auth": "xxxxxx",
			"email": "mskalick"
		},
		"https://registry.access.redhat.com/v1/": {
			"auth": "xxxxxx"
		}
	}
}
8. Now it is possible to push to personal namespace in Docker Hub


I am not sure how projectatomic docker should work. So is my example how it should work?

(In reply to Marek Skalický from comment #2)
> How reproducible:
> 1. system without docker
> 2. yum install docker-1.10.3-59.el7 && systemctl start docker
> 3. docker login docker.io (with your Docker Hub credentials) 
>   In .docker/config.json there is:
> {
> 	"auths": {
> 		"https://index.docker.io/v1/": {
> 			"auth": "xxxxxxxxxx",
> 			"email": "mskalick"
> 		}
> 	}
> }
> 
> 4. Now it is possible to push to personal namespace in Docker Hub
> 5. yum install docker-1.12.5-14.el7
> 6. Now it is NOT possible to push to personal namespace in Docker Hub
> (unauthorized: authentication required; .docker/config.json is the same)

How are you pushing in 4. and 6.? can you show me the command? if you're pushing with just "username/imagename" then it shouldn't work in both 4. and 6. and you must push with "docker.io/username/imagename" since the default registry is "registry.access.redhat.com" when pushing unqualified images (w/o the hostname).

For example with: "docker push docker.io/mskalick/mongodb-32-centos7"

(In reply to Marek Skalický from comment #4)
> For example with: "docker push docker.io/mskalick/mongodb-32-centos7"

so that works with 1.10.3, and .docker/config.json has the docker.io entry but after you upgrade to 1.12.x, even if .docker/config.json has the docker.io entry, that push command doesn't work anymore with unauthorized error?

(In reply to Antonio Murdaca from comment #5)
> so that works with 1.10.3, and .docker/config.json has the docker.io entry
> but after you upgrade to 1.12.x, even if .docker/config.json has the
> docker.io entry, that push command doesn't work anymore with unauthorized
> error?

Exactly.

docker.io entry have to be renamed to "https://registry.access.redhat.com/v1/" to get pushing to Docker Hub working again.

Fixed by:

https://github.com/projectatomic/docker/commit/146d0e3c335143bc156c18bea6332969f71cf6c1
https://github.com/projectatomic/docker/commit/bbfd8436cafdad2eb70fc5ade0ba25ab454ee801

Lokesh, could you rebuild for rhel?

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1325