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

Docker run reports wrong image missing when using --link #39823

Closed
kross-italk opened this issue Aug 29, 2019 · 1 comment · Fixed by #39852
Closed

Docker run reports wrong image missing when using --link #39823

kross-italk opened this issue Aug 29, 2019 · 1 comment · Fixed by #39852
Labels
area/api area/daemon kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. version/19.03

Comments

@kross-italk
Copy link

Description
If you use --link and the linked image isn't running, the top level image you're trying to run reports as not found.

Steps to reproduce the issue:

  1. docker run --link thisdoesntexist python
  2. Unable to find image 'python:latest' locally

Describe the results you received:

The image to run has to already have been built. It is noticed if you run
docker run --link thisdoesntexist python
it first downloads python, then correctly says "unable to find thisdoesntexist" only if python hasn't downloaded before

Describe the results you expected:
Correctly report the linked image name that's missing

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

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:21:05 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       74b1e89
  Built:            Thu Jul 25 21:19:41 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker info:

Client:
 Debug Mode: false

Server:
 Containers: 11
  Running: 4
  Paused: 0
  Stopped: 7
 Images: 89
 Server Version: 19.03.1
 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 ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 4.15.0-55-generic
 Operating System: Ubuntu 18.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.852GiB
 Name: kross
 ID: EPUW:J7KX:4IAV:MMOT:MWDW:GPIT:O32V:U4AO:WQSC:FF53:ZT6K:PLQN
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):

@thaJeztah
Copy link
Member

Thanks for reporting! Pull request with a fix is here: #39852

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api area/daemon kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. version/19.03
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants