8f2629ed85
This is related to an incompatibility between docker and podman.
"docker build" produces image manifests that look like this:
{'config': {'digest': 'sha256:abc',
'mediaType': 'application/vnd.docker.container.image.v1+json'},
'layers': [{'digest': 'sha256:def',
'mediaType': 'application/vnd.docker.image.rootfs.diff.tar.gzip',
'size': 5678},
...
"podman build" manifests look like this:
{'config': {'digest': 'sha256:abc',
'mediaType': 'application/vnd.docker.container.image.v1+json',
'size': 1234},
'layers': [{'digest': 'sha256:def',
'mediaType': 'application/vnd.docker.image.rootfs.diff.tar.gzip',
'size': 5678},
...
Podman includes the size attribute for the image config, but Docker
does not. If you "docker build" and "docker push" to a zuul-registry,
and then "podman pull" from it, it will fail because of the missing
size.
One solution to this would be to simply "podman build" instead of
"docker build". That's probably best.
But somehow, when the result of "docker build" is pushed to Docker Hub,
and then that is used with "podman pull", it works. We can surmise that
Docker Hub is correcting the manifest with the missing data in that case.
To maintain compatability, let's do the same.
Also, add a missing content-type header on blob GETs. This doesn't seem
to be important, but it's more correct.
Change-Id: I0db0dbf9775b02438880624bcf98d2b8f4d2575c
Zuul Registry
This is a container image registry for use with the Zuul project gating system.
The defining feature of this registry is support for shadowing images: it allows you to upload a local version of an image to use instead of an upstream version. If you pull an image from this registry, it will provide the local version if it exists, or the upstream if it does not.
This makes it suitable for use in a Zuul-driven speculative image pipeline.
The latest documentation for Zuul is published at: https://zuul-ci.org/docs/
Getting Help
There are two Zuul-related mailing lists:
- zuul-announce
-
A low-traffic announcement-only list to which every Zuul operator or power-user should subscribe.
- zuul-discuss
-
General discussion about Zuul, including questions about how to use it, and future development.
You will also find Zuul developers in the #zuul channel on Freenode IRC.
Contributing
To browse the latest code, see: https://opendev.org/zuul/zuul-registry To clone the latest code, use git clone https://opendev.org/zuul/zuul-registry
Bugs are handled at: https://storyboard.openstack.org/#!/project/zuul/zuul-registry
Suspected security vulnerabilities are most appreciated if first reported privately following any of the supported mechanisms described at https://zuul-ci.org/docs/zuul/user/vulnerabilities.html
Code reviews are handled by gerrit at https://review.opendev.org
After creating a Gerrit account, use git review to submit patches. Example:
# Do your commits
$ git review
# Enter your username if promptedJoin #zuul on Freenode to discuss development or usage.
License
Zuul-registry is free software licensed under the General Public License, version 3.0.
Python Version Support
Zuul requires Python 3. It does not support Python 2.