Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-1368

Quay does not accept uncompressed layers

XMLWordPrintable

    • 0

      Quay does not accept any container with a manifest that has layers that are not compressed. This causes many problems because Red Hat container tools (podman, skopeo, buildah) do not always produce images with compressed layers.

      This problem is further exacerbated by the default registry within OCP 3 and 4. This registry accepts images with uncompressed layers. Users who are basing builds off default s2i images such as python:3.4[0] encounter failure to push to quay as the base image has a layer with 'application/vnd.docker.image.rootfs.diff.tar' in the manifest.

      While I understand the value in only allow gzipped images from a compute standpoint it is severely limiting the usefulness of Quay in the OCP ecosystem.

      [0] https://docs.openshift.com/container-platform/3.11/using_images/s2i_images/python.html#using-images-s2i-images-python

            Unassigned Unassigned
            kybrown@redhat.com Kyle Brown (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: