moby: GCE Not using already pulled images and errors during pull

Output of docker version:

Client:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:        Sat Jul  2 00:15:19 2016
 OS/Arch:      linux/amd64
 Experimental: true
Server:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:        Sat Jul  2 00:15:19 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:

Server Version: 1.12.0-rc3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 29
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null overlay host bridge
Swarm: active
 NodeID: 0pu0lj4cqvgdsmwr1s0sbi4s1
 IsManager: Yes
 Managers: 1
 Nodes: 1
 CACertHash: sha256:102744b06372a3f1d5ed9cfbf2ffa81861227b3007c74f9342a31f54fcfea202
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.625 GiB
Name: bender-swarm
ID: T7SC:YJT6:PHF5:IFJZ:UW5S:GFLK:XTHV:FNGA:OUBC:GPNQ:FF5Y:HY4R
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Experimental: true
Insecure Registries:
 127.0.0.0/8

Additional environment details (AWS, VirtualBox, physical, etc.): Running on Google Container Engine

Steps to reproduce the issue:

  1. docker login <private registry>
  2. docker pull image <- works fine
  3. docker service create --registry-auth -e <env_file> --name <service> image:tag
  4. Service spins up, but containers cannot spin up. Even if image already available.

Describe the results you received: level=error msg=“Error trying v2 registry: error parsing HTTP 404 response body: invalid character ‘<’ looking for beginning of value: "<!DOCTYPE HTML PUBLIC \\"-//W3C//DTD HTML 3.2 Final//EN\\">\n<title>404 Not Found</title>\n

Not Found

\n

The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

\n"”

level=error msg=“Attempting next endpoint for pull after error: error parsing HTTP 404 response body: invalid character ‘<’ looking for beginning of value: "<!DOCTYPE HTML PUBLIC \\"-//W3C//DTD HTML 3.2 Final//EN\\">\n<title>404 Not Found</title>\n

Not Found

\n

The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

\n"”

level=error msg=“Not continuing with pull after error: unauthorized: authentication required” level=error msg=“pulling image failed” error=“unauthorized: authentication required” level=error msg=“fatal task error” error=“No such image: image:tag”

Describe the results you expected: Expect image used if available or pulls using same credentials successfully. I feel like this just became an issue this week as I was successfully starting up the service early the week prior.

Additional information you deem important (e.g. issue happens only occasionally):

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 16 (10 by maintainers)

Most upvoted comments

@charliekump-wf Can you post the full daemon logs and the specific image name. I wonder if the image name gets corrupted for some reason and request to pull goes to a wrong address. If you can, please post registry logs also. If you can reproduce this with v2 registry and without authorization, then this would be simplest for us to debug.