docker manifest create returns 'no such manifest'
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
docker manifest create returns 'no such manifest'
Steps to reproduce the issue:
- build docker multiple docker images
- create a docker manifest with created docker images
- error
Describe the results you received:
no such manifest: 192.168.5.223:5000/authserver-amd64:v0.0.1
Describe the results you expected:
As described by the docs, to be able to push this manifest to a docker registry and use the multiarch image
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
Version: 19.03.7-ce
API version: 1.40
Go version: go1.14
Git commit: 7141c199a2
Built: Fri Mar 6 12:42:12 2020
OS/Arch: linux/amd64
Experimental: true
Server:
Engine:
Version: 19.03.7-ce
API version: 1.40 (minimum version 1.12)
Go version: go1.14
Git commit: 7141c199a2
Built: Fri Mar 6 12:41:47 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.3.3.m
GitCommit: d76c121f76a5fc8a462dc64594aea72fe18e1178.m
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Output of docker info:
Client:
Debug Mode: false
Server:
Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 98
Server Version: 19.03.7-ce
Storage Driver: overlay2
Backing Filesystem: <unknown>
Supports d_type: true
Native Overlay Diff: false
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: d76c121f76a5fc8a462dc64594aea72fe18e1178.m
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 5.5.8-1-MANJARO
Operating System: Manjaro Linux
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 15.65GiB
Name: pc
ID: TG4H:YFRI:Q74H:LFVA:FALY:IFXO:GU2R:HYMC:YVVN:ZZME:4YWY:3PDN
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
192.168.5.223:5000
127.0.0.0/8
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.):
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the docker manifest create command and reproduce the reported steps using the supplied Docker 19.03.7 environment and registry image reference. Determine why an existing image is reported as no such manifest; done means the documented multi-architecture manifest can be created and pushed successfully, with coverage for the failure case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100