Description
Perfoming a Docker build where the base image is pulled from a private (artifactory) registry reports that the manifest for the base image is not found.
Docker Desktop provides an integrated container-native development experience; it launches as an application from your Mac or Windows toolbar and provides access to the largest library of community and certified Linux and Windows Server content from Docker Hub.
Steps to reproduce the issue:
- Create a simple Dockerfile with only the FROM directive pointing to an image in our private Artifactory Docker registry
- Run the docker build command within a terminal window.
Describe the results you received:
The build immediately fails at Step 1 (FROM directive) and reports that the manifest for the specified image can't be found.
Describe the results you expected:
Normally you would expect to see the image layers starting to be downloaded.
Additional information you deem important (e.g. issue happens only occasionally):
Docker push and pull requests work as expected, as well as tagging operations from the command line. The docker daemon had to have the --disable-legacy-registry flag set to true.
Output of
docker version
:Client:
Version: 17.03.1-ce
API version: 1.27
Go version: go1.7.5
Git commit: c6d412e
Built: Tue Mar 28 00:40:02 2017
OS/Arch: darwin/amd64
Version: 17.03.1-ce
API version: 1.27
Go version: go1.7.5
Git commit: c6d412e
Built: Tue Mar 28 00:40:02 2017
OS/Arch: darwin/amd64
Server:
Version: 17.03.1-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: c6d412e
Built: Fri Mar 24 00:00:50 2017
OS/Arch: linux/amd64
Experimental: false
Version: 17.03.1-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: c6d412e
Built: Fri Mar 24 00:00:50 2017
OS/Arch: linux/amd64
Experimental: false
Output of
docker info
:Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 17.03.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: 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: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.13-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.952 GiB
Name: moby
ID: K7LV:35QB:7KX4:BYQV:NIZI:KXQN:WJFK:DICW:OKEG:4CS5:XIIQ:6KBC
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 17
Goroutines: 28
System Time: 2017-04-11T20:25:55.607210575Z
EventsListeners: 1
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 17.03.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: 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: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.13-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.952 GiB
Name: moby
ID: K7LV:35QB:7KX4:BYQV:NIZI:KXQN:WJFK:DICW:OKEG:4CS5:XIIQ:6KBC
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 17
Goroutines: 28
System Time: 2017-04-11T20:25:55.607210575Z
EventsListeners: 1
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.):
Private registry is hosted in AWS on jFrog Artifactory Version 4.14.2.
![Docker registry https Docker registry https](/uploads/1/2/5/2/125281914/695115325.png)
![Docker For Mac Disable-legacy-registry Docker For Mac Disable-legacy-registry](/uploads/1/2/5/2/125281914/405759784.png)
Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upHave 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
Comments
commented Dec 31, 2015
When I typed docker --help , it shown as below:I think every option is appropriate except -disable-legacy-registry which is an flag for docker daemon and looks a little strange here, I think it should not appear here. |
commented Dec 31, 2015
/cc @RichardScothern, who added this in #16385 |
commented Jan 4, 2016
Interesting. I do not see this with 1.9.0 :@thaJeztah: any ideas? |
commented Jan 4, 2016
@RichardScothern hm, perhaps the difference is that the Darwin version is a client-only build? What do you get if you docker-machine ssh default and run it inside the VM? |
commented Jan 4, 2016
Your theory is correct - the flag does appear in the VM build. As far as I remember, this flag was added before the daemon subcommand was added (I could be wrong). This flag belongs only on the daemon. |
referenced this issue Jan 4, 2016
MergedShow the legacy registry flag only in the daemon arguments #19064
added a commit to chenbo1989/docker that referenced this issue Jan 13, 2016
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment