microsoft / aspnet-docker

This repository has moved to microsoft/dotnet-framework-docker.
https://github.com/Microsoft/dotnet-framework-docker
MIT License
135 stars 73 forks source link

unauthorized: authentication required #86

Closed natemcmaster closed 6 years ago

natemcmaster commented 6 years ago

From @eliassal on January 17, 2018 8:37

Hi, whenever I try docker pull microsoft/aspnet, I get

Sending build context to Docker daemon  24.06kB
Step 1/7 : FROM microsoft/aspnet
latest: Pulling from microsoft/aspnet
3889bb8d808b: Downloading [=====>                                             ]    446MB/4.07GB
449343c9d7e2: Downloading [=================>                                 ]  445.9MB/1.304GB
ccd8f322a2de: Download complete
5358f1f8c04f: Download complete
27fb1950158d: Download complete
4447c3ffe068: Download complete
94eeeaf0d3bd: Download complete
fe1d276c8d64: Downloading
25871a4250c9: Waiting
b53cc298d0b7: Waiting
unauthorized: authentication required

any help? Opened a thread on docker site, nobody responded. My platform is Docker for windows as follows

Client: Version: 17.12.0-ce API version: 1.35 Go version: go1.9.2 Git commit: c97c6d6 Built: Wed Dec 27 20:05:22 2017 OS/Arch: windows/amd64

Server: Engine: Version: 17.12.0-ce API version: 1.35 (minimum version 1.24) Go version: go1.9.2 Git commit: c97c6d6 Built: Wed Dec 27 20:15:52 2017 OS/Arch: windows/amd64

If you are having an issue with microsoft/aspnet, please open an issue on https://github.com/Microsoft/aspnet-docker. This repository is for microsoft/aspnetcore and microsoft/aspnetcore-build.

Steps to reproduce the issue

(e.g. copy your Dockerfile or docker-compose.yml file here) 1. 2. 3.

Expected behavior

Actual behavior

Additional information (e.g. issue happens only occasionally)

Output of dotnet --info

(paste your output here)

Output of docker info

(paste your output here)

Copied from original issue: aspnet/aspnet-docker#352

natemcmaster commented 6 years ago

From @eliassal on January 17, 2018 8:47

Just to confirm that win 10 firewall is completely desactivated

eliassal commented 6 years ago

Any feedback team? I am really blocked on progressing on my POC

natemcmaster commented 6 years ago

cc @MichaelSimons @richlander

MichaelSimons commented 6 years ago

@eliassal - Are you able to pull any images (e.g. microsoft/nanoserver or microsoft/dotnet)?

eliassal commented 6 years ago

microsoft/dotnet went through

PS E:\Projects> docker pull microsoft/dotnet Using default tag: latest latest: Pulling from microsoft/dotnet bce2fbc256ea: Already exists 764aee428c28: Pull complete 8371a170f55a: Pull complete 5c024c6ed680: Pull complete eb356354ca8e: Pull complete 68e4c67671a1: Pull complete e023682a40b1: Pull complete d8ac9d7c29ce: Pull complete 461bf4c2d94c: Pull complete d3f3bf93c06a: Pull complete Digest: sha256:5483e2b609c0f66c3ebd96666de7b0a74537613b43565879ecb0d0a73e845d7d Status: Downloaded newer image for microsoft/dotnet:latest

docker pull microsoft/aspnet from 2 win10 machines 1st one has "Windows on docker", the 2nd has windows for Docker", outcome exactly the same

Using default tag: latest latest: Pulling from microsoft/aspnet

3889bb8d808b: Already exists 449343c9d7e2: Downloading [======> ] 159 MB/1.304 GB ccd8f322a2de: Downloading [=========> ] 144.3 MB/760.6 MB 5358f1f8c04f: Download complete 27fb1950158d: Download complete 4447c3ffe068: Downloading 94eeeaf0d3bd: Waiting fe1d276c8d64: Waiting 25871a4250c9: Waiting b53cc298d0b7: Waiting unauthorized: authentication required

MichaelSimons commented 6 years ago

@eliassal - can you include the output from docker info?

eliassal commented 6 years ago

Michael, I switched to "linux container" mode, whatever command I issue I get

PS E:\Projects> docker run -d -p 80:80 --name webserver nginx Unable to find image 'nginx:latest' locally latest: Pulling from library/nginx C:\Program Files\Docker\Docker\Resources\bin\docker.exe: no matching manifest for windows/amd64 in the manifest list entries.

What is wrong with this docker, I did an update last week to last version

MichaelSimons commented 6 years ago

Are you sure you are in "linux container" mode? The error indicates you are in "windows container" mode. What does docker version -f "{{ .Server.Os }}" show?

eliassal commented 6 years ago

Docker info for the VM that has Docker for windows

PS E:\Projects> docker info Containers: 5 Running: 0 Paused: 0 Stopped: 5 Images: 3 Server Version: 17.12.0-ce Storage Driver: windowsfilter Windows: Logging Driver: json-file Plugins: Volume: local Network: ics l2bridge l2tunnel nat null overlay transparent Log: awslogs etwlogs fluentd gelf json-file logentries splunk syslog Swarm: inactive Default Isolation: hyperv Kernel Version: 10.0 14393 (14393.2007.amd64fre.rs1_release.171231-1800) Operating System: Windows 10 Enterprise OSType: windows Architecture: x86_64 CPUs: 1 Total Memory: 5.499GiB Name: winForDocker ID: 7U5G:CCGF:VKFI:QTV7:MYCB:F2YK:5KNS:ZVLG:KEIN:PGYO:YX43:WPTY Docker Root Dir: E:\Docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

Docker info for the VM that has docker on windows 10

Containers: 8 Running: 1 Paused: 0 Stopped: 7 Images: 56 Server Version: 1.13.0-dev Storage Driver: windowsfilter Windows: Logging Driver: json-file Plugins: Volume: local Network: l2bridge l2tunnel nat nat null null transparent transparent Swarm: inactive Default Isolation: hyperv Kernel Version: 10.0 15063 (15063.0.amd64fre.rs2_release.170317-1834) Operating System: Windows 10 Enterprise OSType: windows Architecture: x86_64 CPUs: 4 Total Memory: 15.86 GiB Name: sierac ID: DUSB:JZ46:WIJ5:BCQP:DGVT:TV3X:BP7X:4VWU:CTF2:U7A6:HVXN:HZLB Docker Root Dir: E:\Hyper-V\DockerMachines Debug Mode (client): false Debug Mode (server): false Username: eliassal Registry: https://index.docker.io/v1/ Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Containers: 8 Running: 1 Paused: 0 Stopped: 7 Images: 56 Server Version: 1.13.0-dev Storage Driver: windowsfilter Windows: Logging Driver: json-file Plugins: Volume: local Network: l2bridge l2tunnel nat nat null null transparent transparent Swarm: inactive Default Isolation: hyperv Kernel Version: 10.0 15063 (15063.0.amd64fre.rs2_release.170317-1834) Operating System: Windows 10 Enterprise OSType: windows Architecture: x86_64 CPUs: 4 Total Memory: 15.86 GiB Name: sierac ID: DUSB:JZ46:WIJ5:BCQP:DGVT:TV3X:BP7X:4VWU:CTF2:U7A6:HVXN:HZLB Docker Root Dir: E:\Hyper-V\DockerMachines Debug Mode (client): false Debug Mode (server): false Username: eliassal Registry: https://index.docker.io/v1/ Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

eliassal commented 6 years ago

The outpot of docker version -f "{{ .Server.Os }}" is WINDOWS, but right clicking the whale, it shws "Switch to Windows" which means I switched to windows as you can notice in the snapshot , strange No? dockeswitch

MichaelSimons commented 6 years ago

Something definitely seems wrong with the state of Docker or your Docker installation in general. Possibly restart docker or the machine. This issue in general seems Docker related and not something specific to microsoft/aspnet. https://github.com/moby/moby is the place to log Docker issues like this.

eliassal commented 6 years ago

OK, I will remove completely docker and reinstall.

eliassal commented 6 years ago

Michael, it is happening on 2 different win10 machines with different versions of docker, I a, not sure it is related to docker. What I will do is that I will setup docker for windows on a 3rd win10 machine and see

eliassal commented 6 years ago

Yes Michael, you are correct, it seems that docker on this win1 is corrupt, and I think it is related to the many updates done over the year. I setup Docker for windows on a third win10 machine and everything went through

eliassal commented 6 years ago

Michael, I did a clean setup, removed Docker for windows, deleted all related data, reinstalled getting the exact same error

eliassal commented 6 years ago

I opened a thred on but again when I do

docker pull microsoft/nanoserver

it works fine without any issue

natemcmaster commented 6 years ago

Closing as this issue is stale and the cause of the issue appears to be an intermittent problem with docker.