profile
viewpoint

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


GENERAL SUPPORT INFORMATION

The GitHub issue tracker is for bug reports and feature requests. General support for docker can be found at the following locations:

  • Docker Support Forums - https://forums.docker.com
  • Slack - community.docker.com #general channel
  • Post a question on StackOverflow, using the Docker tag

General support for moby can be found at the following locations:

  • Moby Project Forums - https://forums.mobyproject.org
  • Slack - community.docker.com #moby-project channel
  • Post a question on StackOverflow, using the Moby tag

BUG REPORT INFORMATION

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 -->

Description

<!-- 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:

  1. docker tag nginx quay.io/vvoody/test:nginx
  2. docker push quay.io/vvoody/test:nginx

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 quay.io.

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.

Logs said 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.

Output of docker version:

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

Output of docker info:

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.

moby/moby

Answer questions vvoody

@cpuguy83 and @jacobmarble, thanks for the information!

useful!

Related questions

start container failed with "failed to umount /var/lib/docker/containers/.../shm: no such file or directory" hot 241
start container failed with "failed to umount /var/lib/docker/containers/.../shm: no such file or directory" hot 176
upgrade docker-18.09.2-ce , shim.sock: bind: address already in use: unknown hot 83
Windows Server 2019 publish ports in swarm not working hot 70
OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown hot 59
integration: "error reading the kernel parameter" errors during CI hot 58
write unix /var/run/docker.sock->@: write: broken pipe hot 57
Swarm restarts all containers hot 56
hcsshim::PrepareLayer failed in Win32: The parameter is incorrect hot 52
Error response from daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded hot 50
runc regression - EPERM running containers from selinux hot 50
"docker stack deploy">"rpc error: code = 3 desc = name must be valid as a DNS name component" hot 41
Can't set net.ipv4.tcp_tw_reuse in docker 1.10.3 hot 40
Docker stack fails to allocate IP on an overlay network, and gets stuck in `NEW` current state hot 38
Docker 18.09.1 doesn't work with iptables v1.8.2 hot 35
Github User Rank List