-
Notifications
You must be signed in to change notification settings - Fork 45
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
podman pull from pulp fails with: unsupported schema version 2 #883
Comments
I'd consider this relatively important for Katello. @ipanova do you anticipate other container images being affected by this? So far we're only seeing the ceph-zabbix one. |
@ianballou yes, oci container images that do not contain mediatype as part of manifest.json. We'll get this fixed and backport where it's needed. |
@ianballou to what branch do you want this fix backported? |
@ipanova 2.10 and 2.9 as well if possible. |
Steps to reproduce
http https://pulp3-source-fedora34.fluffy.example.com/pulp/api/v3/remotes/container/container/ name=lala upstream_name=riadh_hamdi/ceph-zabbix url=https://quay.io
http https://pulp3-source-fedora34.fluffy.example.com/pulp/api/v3/distributions/container/container/ name=ina base_path=ina repository_version= /pulp/api/v3/repositories/container/container/dc8ce8e4-1cc0-495c-be5d-513e63dd931d/versions/1/
podman --log-level=debug pull pulp3-source-fedora34.fluffy.example.com/ina
There is a discrepancy from what we store in DB and the actual manifest.json artifact
Note schema_version and media_type stored in DB vs that it is an OCI image in reality.
Root cause
This is the offending line https://github.com/pulp/pulp_container/blob/main/pulp_container/app/tasks/sync_stages.py#L352 and https://github.com/pulp/pulp_container/blob/main/pulp_container/app/tasks/sync_stages.py#L132
Based on the specs
mediaType
is not a required field for the oci image https://github.com/opencontainers/image-spec/blob/main/manifest.md#image-manifest-property-descriptionsThe text was updated successfully, but these errors were encountered: