Ask questionsmanifest invalid error when pushing image to quay.io
<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see https://github.com/moby/moby/blob/master/CONTRIBUTING.md#reporting-other-issues
The GitHub issue tracker is for bug reports and feature requests. General support for docker can be found at the following locations:
General support for moby can be found at the following locations:
Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->
<!-- Briefly describe the problem you are having in a few paragraphs. -->
Unable to push image to registry hosted at
quay.io in docker-ce 19.03.0-beta4.
Steps to reproduce the issue:
Describe the results you received:
The push refers to repository [quay.io/vvoody/test] 62491c1227dd: Pushed b3f4f4d8f801: Pushed 2ddf52a320d2: Pushed 16174e87921f: Pushed manifest invalid: manifest invalid
Describe the results you expected:
Image OK to push to
Additional information you deem important (e.g. issue happens only occasionally):
This issue occurs when use docker-ce 19.03.0-beta4 to push image to quay.io. However, it's good for pushing to hub.docker.io.
And docker-ce 18.03.0 and 18.09.2 are also able to push image to quay.io.
level=warning msg="failed to upload schema2 manifest: manifest invalid: manifest invalid".
I found https://github.com/moby/moby/issues/27580 reported for same
manifest invalid issue. It looks resolved. And everything was good before I tried 19.03.0-beta4.
Client: Docker Engine - Community Version: 19.03.0-beta4 API version: 1.40 Go version: go1.12.4 Git commit: e4666eb Built: Tue May 14 12:51:53 2019 OS/Arch: linux/amd64 Experimental: false Server: Docker Engine - Community Engine: Version: 19.03.0-beta4 API version: 1.40 (minimum version 1.12) Go version: go1.12.4 Git commit: e4666eb Built: Tue May 14 12:50:26 2019 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.2.5 GitCommit: bb71b10fd8f58240ca47fbb579b9d1028eea7c84 runc: Version: 1.0.0-rc6+dev GitCommit: 2b18fe1d885ee5083ef9f0838fee39b62d653e30 docker-init: Version: 0.18.0 GitCommit: fec3683
Client: Debug Mode: false Plugins: app: Docker Application (Docker Inc., v0.8.0-beta2) Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 1 Server Version: 19.03.0-beta4 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: bb71b10fd8f58240ca47fbb579b9d1028eea7c84 runc version: 2b18fe1d885ee5083ef9f0838fee39b62d653e30 init version: fec3683 Security Options: apparmor seccomp Profile: default Kernel Version: 4.4.0-142-generic Operating System: Ubuntu 16.04.5 LTS OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 992MiB Name: ubuntu-xenial ID: f7ad9380-11fa-46a7-be23-348b3cc87628 Docker Root Dir: /var/lib/docker Debug Mode: true File Descriptors: 21 Goroutines: 34 System Time: 2019-05-15T09:37:01.146190131Z EventsListeners: 0 Username: vvoody 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.):
Ubuntu 16.04 on VirtualBox.
Answer questions vvoody
@cpuguy83 and @jacobmarble, thanks for the information!