aspnet / aspnet-docker

[Archived] ASP.NET Core Docker images for 1.x. Go to https://github.com/dotnet/dotnet-docker for 2.1 and up.
https://asp.net
719 stars 171 forks source link

Cannot pull new 2.0 build image #282

Closed testJunkie closed 7 years ago

testJunkie commented 7 years ago

Steps to reproduce the issue

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

  1. docker pull microsoft/aspnetcore-build:2

Expected behavior

Pulls the docker image successfully.

Actual behavior

2: Pulling from microsoft/aspnetcore-build 06b22ddb1913: Already exists 336c28b408ed: Pull complete 1f3e6b8d80c3: Pull complete 5ccc640979f6: Pull complete ddd2eeb54216: Pull complete f40f8d815820: Downloading [=====================> ] 59.47MB/137.2MB 94ef1b31dbc2: Downloading [======> ] 33.52MB/276.3MB 7913b285556d: Download complete 5a9f325426bd: Download complete 7527523c13ce: Download complete fdead1149eb4: Downloading 8f563f50bb56: Waiting unauthorized: authentication required

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

This happens on layer "fdead1149eb4" every time.

Output of docker info

Containers: 2 Running: 2 Paused: 0 Stopped: 0 Images: 5 Server Version: 17.05.0-ce Storage Driver: overlay Backing Filesystem: xfs Supports d_type: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 9048e5e50717ea4497b757314bad98ea3763c145 runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228 init version: 949e6fa Security Options: seccomp Profile: default Kernel Version: 3.10.0-514.26.2.el7.x86_64 Operating System: CentOS Linux 7 (Core) OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 3.907GiB Name: CentOS7Dev ID: YOVA:NXJC:FVCA:SCKN:45P2:BLAQ:U5TT:5MM3:IZSM:INL5:3KYR:JVPD Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Username: privtestdocker Registry: https://index.docker.io/v1/ Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

testJunkie commented 7 years ago

The nightly build has resolved this.