-
Notifications
You must be signed in to change notification settings - Fork 43
Description
Description of problem
Issues with ‘docker login’ on Windows.
The command returns Status Code 403 – Request forbidden by administrative rules.
Docker version
1.9.1-rc1
Docker info
# Environment details (AWS, VirtualBox, physical, etc.):Vritual Box Provider
How reproducible:
Just input ‘docker login’ into CLI without adding any providers.
Steps to Reproduce:
- open CLI on Windows
- docker login
- check return
Actual Results:
Error response from daemon: "Unexpected status code [403] - <html><body><h1> 403 Fobidden</h1> Request forbidden by administrative rules. </body></html>"
Successful login into Docker default registry for Windows and full integration with docker hub.
Additional info:
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.
- Environment Windows + Docker Login with https://registry-win-tp3.docker.io/v1/
- Returns Request forbidden by administrative rules
- Environment Windows + Docker Login with https://index.docker.io/v1/
- Login succeeds.
- Still can’t docker push. Command returns: unauthorized: access to the requested resource is not authorized.
Actually, checking the code, I could not detect an actual problem with the docker/docker but maybe it’s an registry issue.
Important: I've opened this same issue at Docker/Docker early but after some tests we find out that this happens ONLY with the dockerHub Service. Tests with Tutum and Quay.io were successful.

