Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Issue with docker login & push with Docker Default Registry - Windows ENV - 1.9.1-RC1 #18019
Description of problem
Issues with ‘docker login’ on Windows.
Vritual Box Provider
Just input ‘docker login’ into CLI without adding any providers.
Steps to Reproduce:
Successful login into Docker default registry for Windows and full integration with docker hub.
After some analysis of the source code I’ve detected that we have different registry URLs for Windows and UNIX.
I’m using the freshly baked 1.9.1-rc1
While both urls are responding to requests, playing with docker login and those data, i could notice two different behaviors.
Actually, checking the code, I could not detect an actual problem with the docker/docker but maybe it’s an registry issue.
I'm proceed into double checking the functionality with other Registry.
My examples used the basic Getting Started Guide for the sake of understanding: http://docs.docker.com/mac/step_six/
Actually I’m a docker newbie but in love with the project and looking forward into contributing. I could be missing something so, feel free to shed some light into my ramblings.
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
Same problem here.
When using docker login --username=* --password=* --email=****
When using simple docker login:
@JigSawFr Same here!
Considering the auth options supported by Registry (Native Basic, Proxy or Delegated as explained here), i'm inclined the believe that this issue is not related to Registry's code - maybe we're just facing an infraestructure problem on the 'authentication layer' of https://registry-win-tp3.docker.io/v1/.
That said, i think this problem should be reported at 'hub-feedback' as well.
I am having the same issues as others have mentioned above when following Windows demo\example.
same issue here as well.
same issue here too
$ docker version
$ docker info
$ uname -a
Didn't work for me. I had a Docker Hub account that I created a while back, but forgot my password for. I changed my password today, created a new private repo, and I get all the variety of issues described above. I have tried creating a .dockercfg manually (since I never had one to begin with), but that did not work, either. Trying to pull the repo I created says it's not found as well.
Thanks for the info @JigSawFr!
Using that workaround i can login successfully at DockerHub using the default unix registry but, when i try to push, docker says that my repos doesn't exist (Repository does not exist: miguelmf/[anyrepo]).
I'll make some tests here and see if i can solve this one.
Found the solution:
To get docker to create the config.json file, I had to first run:
docker login --username= --email= https://index.docker.io/v1/
Then, I was able to modify the config.json file as shown here:
Everything is now working.