Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with docker login & push with Docker Default Registry - Windows ENV - 1.9.1-RC1 #18019

Closed
Miguel-Fontes opened this issue Nov 16, 2015 · 29 comments

Comments

@Miguel-Fontes
Copy link

@Miguel-Fontes Miguel-Fontes commented Nov 16, 2015

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

docker_meta

# Environment details (AWS, VirtualBox, physical, etc.):

Vritual Box Provider

How reproducible:

Just input ‘docker login’ into CLI without adding any providers.

Steps to Reproduce:

  1. open CLI on Windows
  2. docker login
  3. 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>"

login_forbidden_all

### Expected Results:

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.

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.

@GordonTheTurtle

This comment has been minimized.

Copy link

@GordonTheTurtle GordonTheTurtle commented Nov 16, 2015

Hi!

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.

Thank you.

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:

docker version:
docker info:
uname -a:

Provide additional environment details (AWS, VirtualBox, physical, etc.):

List the steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Provide additional info you think is important:

----------END REPORT ---------

#ENEEDMOREINFO

@stevesri

This comment has been minimized.

Copy link

@stevesri stevesri commented Nov 17, 2015

I have the same issue.

@Dinosys

This comment has been minimized.

Copy link

@Dinosys Dinosys commented Nov 17, 2015

Same problem here.

When using docker login --username=* --password=* --email=****
format:

$ docker login --username=*******--password=<pass> --email=<email>
Error response from daemon: Unexpected status code [403] : <html><body><h1>403 Forbidden</h1>
Request forbidden by administrative rules.
</body></html>

When using simple docker login:

$ docker login
Username: ******
The handle is invalid.

docker version:

Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   76d6bc9
 Built:        Tue Nov  3 19:20:09 UTC 2015
 OS/Arch:      windows/amd64

Server:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   76d6bc9
 Built:        Tue Nov  3 19:20:09 UTC 2015
 OS/Arch:      linux/amd64

docker info:

Containers: 38
Images: 33
Server Version: 1.9.0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 109
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-boot2docker
Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: DIQV:M65R:NVEQ:ZOSQ:SR2O:UP6J:JI3D:MXCJ:MJQF:SFKN:AOOX:QBDE
Debug mode (server): true
 File Descriptors: 13
 Goroutines: 19
 System Time: 2015-11-17T08:19:48.385329072Z
 EventsListeners: 0
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=virtualbox

uname -a

MINGW64_NT-6.1 BA91-CND5268397 2.1.0(0.288/5/3) 2015-06-28 18:57 x86_64 Msys
@JigSawFr

This comment has been minimized.

Copy link

@JigSawFr JigSawFr commented Nov 17, 2015

Same issue too.

@likfarmenhet

This comment has been minimized.

Copy link

@likfarmenhet likfarmenhet commented Nov 17, 2015

Same issue here

@JigSawFr

This comment has been minimized.

Copy link

@JigSawFr JigSawFr commented Nov 17, 2015

Registry problem confirmed.
Tested with tutum.co registry with no problems,
Docker image pushed correctly.

@aaronbarzilai

This comment has been minimized.

Copy link

@aaronbarzilai aaronbarzilai commented Nov 17, 2015

I have the same issue as well. Looking forward to seeing this corrected, otherwise docker is working quite well for me.

Thanks,
Aaron

@Miguel-Fontes

This comment has been minimized.

Copy link
Author

@Miguel-Fontes Miguel-Fontes commented Nov 17, 2015

@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.

sem titulo

@diamxus

This comment has been minimized.

Copy link

@diamxus diamxus commented Nov 17, 2015

I am having the same issues as others have mentioned above when following Windows demo\example.
Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: windows/amd64

Server:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: linux/amd64

@reyabreu

This comment has been minimized.

Copy link

@reyabreu reyabreu commented Nov 18, 2015

same issue here as well.

uname@hostname MINGW64 /c/work/hello-docker
$ docker login -u <uname> -p <password> -e <email>
Error response from daemon: Unexpected status code [403] : <html><body><h1>403 F
orbidden</h1>
Request forbidden by administrative rules.
</body></html>

uname@hostname MINGW64 /c/work/hello-docker
$ docker version
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   76d6bc9
 Built:        Tue Nov  3 19:20:09 UTC 2015
 OS/Arch:      windows/amd64

Server:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   76d6bc9
 Built:        Tue Nov  3 19:20:09 UTC 2015
 OS/Arch:      linux/amd64

uname@hostname MINGW64 /c/work/hello-docker
$ docker info
Containers: 0
Images: 22
Server Version: 1.9.0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 22
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-boot2docker
Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:
49:22 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: R2LG:LMA5:BAAY:YTZB:RB4P:N5L7:MDOI:DI6O:33V2:X35I:OKHW:XV7X
Debug mode (server): true
 File Descriptors: 12
 Goroutines: 20
 System Time: 2015-11-18T12:03:46.800984642Z
 EventsListeners: 0
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=virtualbox
@lvendrame

This comment has been minimized.

Copy link

@lvendrame lvendrame commented Nov 18, 2015

same issue here too

$ docker version

Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: windows/amd64

Server:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: linux/amd64

$ docker info

Containers: 7
Images: 14
Server Version: 1.9.0
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 28
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-boot2docker
Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov 3 19:49:22 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: RXO4:BZTI:NLLT:42X3:U7OD:2QIF:GP73:DI3H:4JBO:WAYZ:OOJV:Y4DL
Debug mode (server): true
File Descriptors: 11
Goroutines: 20
System Time: 2015-11-18T16:29:10.800814501Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
provider=virtualbox

$ uname -a

MINGW64_NT-10.0 DESKTOP-NHI74HQ 2.1.0(0.288/5/3) 2015-06-28 18:57 x86_64 Msys

@JigSawFr

This comment has been minimized.

Copy link

@JigSawFr JigSawFr commented Nov 19, 2015

Related to : docker/hub-feedback#473 ➡️
With work around

@VathsalaAchar

This comment has been minimized.

Copy link

@VathsalaAchar VathsalaAchar commented Nov 20, 2015

@JigSawFr Thanks the above fix worked!

@FacioRatio

This comment has been minimized.

Copy link

@FacioRatio FacioRatio commented Nov 23, 2015

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.

@Miguel-Fontes

This comment has been minimized.

Copy link
Author

@Miguel-Fontes Miguel-Fontes commented Nov 24, 2015

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.

@thaJeztah thaJeztah added the kind/bug label Dec 31, 2015
@lucasvc

This comment has been minimized.

Copy link

@lucasvc lucasvc commented Jan 13, 2016

@FacioRatio The correct configuration file is %USERPROFILE%\.docker\config.json. It worked for me.

@tyagian

This comment has been minimized.

Copy link

@tyagian tyagian commented Jan 18, 2016

Found the solution:
We need to add registry authentication function to config.jason file. It's working for me.
http://networkengg.com/docker-login-failed-on-windows-403-forbidden-error/

@siripuramrk

This comment has been minimized.

Copy link

@siripuramrk siripuramrk commented Jan 18, 2016

Thanks @JigSawFr! Working 👍

#######
docker login --username=myuser --password=mypassword --email=myemail https://index.docker.io/v1/
WARNING: login credentials saved in C:\Users\myuser.docker\config.json
Login Succeeded
#######

@ghost

This comment has been minimized.

Copy link

@ghost ghost commented Jan 27, 2016

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:

http://networkengg.com/docker-login-failed-on-windows-403-forbidden-error/

Everything is now working.

@tshepotema

This comment has been minimized.

Copy link

@tshepotema tshepotema commented Jan 28, 2016

docker/hub-feedback#473 <-- This worked for me

docker-push

@reyabreu

This comment has been minimized.

Copy link

@reyabreu reyabreu commented Feb 2, 2016

Overdue thanks to @JigSawFr. Got it working 👍

@Wind4Greg

This comment has been minimized.

Copy link

@Wind4Greg Wind4Greg commented Feb 2, 2016

Still broken as of 2/2/2016, with brand new docker install on windows.

@tiborvass

This comment has been minimized.

Copy link
Collaborator

@tiborvass tiborvass commented Feb 2, 2016

@Wind4Greg it's merged and will be released in 1.10 coming this week

@Wind4Greg

This comment has been minimized.

Copy link

@Wind4Greg Wind4Greg commented Feb 2, 2016

When will it be released/where can I get it?

@thaJeztah

This comment has been minimized.

Copy link
Member

@thaJeztah thaJeztah commented Feb 2, 2016

@Wind4Greg we're planning on releasing docker 1.10.0-rc3 today; hopefully, final release on Thursday

@gerrytan

This comment has been minimized.

Copy link

@gerrytan gerrytan commented Feb 4, 2016

Also affected by this problem. Pretty bad because everyone who's following the getting started tutorial would've been stuck by this

@atipal

This comment has been minimized.

Copy link

@atipal atipal commented Feb 4, 2016

Strange issue. Can't finish the tutorial 👎

@friism

This comment has been minimized.

Copy link
Contributor

@friism friism commented Feb 4, 2016

@gerrytan @atipal @Wind4Greg 1.10 is ready now and fixes this problem, you can get it here: https://github.com/docker/toolbox/releases/tag/v1.10.0

@cvugrinec

This comment has been minimized.

Copy link

@cvugrinec cvugrinec commented May 31, 2016

docker-machine upgrade [name of your instance] fixed it for me...if that does not work try moving your ~/.docker/config.json in /tmp ...when you do docker login it will recreate this file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.