Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support pulling/pushing OCI manifests from a docker registry #338

Merged
merged 2 commits into from
Sep 7, 2017
Merged

Support pulling/pushing OCI manifests from a docker registry #338

merged 2 commits into from
Sep 7, 2017

Commits on Sep 5, 2017

  1. ImageReference.NewImageSource: remove requestedManifestMIMETypes para… 

    …meter

The requestedManifestMIMETypes parameter was added because a destination
might not support all manifest MIME types that the the source supports,
but the original use case now passes all manifest types and lets
containers/image convert internally. In generally, internal conversion
may be more comprehensive, is more predictable, and avoids bypassing
internal checks.

Fixes: containers#331
Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
    @owtaylor
    owtaylor committed Sep 5, 2017
    Configuration menu
    Copy the full SHA
    56b61ac View commit details
    Browse the repository at this point in the history

  2. docker_image_dest: Add OCI manifests to manifestMIMETypes 

    Since OCI support is in progress for the docker registry, if we have
an OCI manifest, we should try uploading it literally to the registry
before falling back to converting it to a v2 manifest.

Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
    @owtaylor
    owtaylor committed Sep 5, 2017
    Configuration menu
    Copy the full SHA
    ae52c73 View commit details
    Browse the repository at this point in the history