-
Notifications
You must be signed in to change notification settings - Fork 779
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
manifest: unable to create from oci path #2858
Comments
If you push while giving it a tag, it does re-import correctly. $ buildah manifest push --all -f v2s2 --purge my-list oci:oci:latest
$ buildah manifest create --all my-list2 oci:oci
8fe16205d301946fcaa8691bdbe4fe5ea0ad52404e31d939603ae3cce3ccba29 If the tag is required, it should probably be enforced on exporting. |
Since I have been playing with manifest I guess I will take this one. |
A friendly reminder that this issue had no activity for 30 days. |
Could you check this against the current master branch, I believe it works now, reopen if I am mistaken. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I'm unable to create a manifest list from an OCI path created by buildah.
Steps to reproduce the issue:
Describe the results you received:
Got an error message unable to import the list exported. I can see
index.json
points at a "application/vnd.docker.distribution.manifest.list.v2+json" like expected.Describe the results you expected:
Buildah should be able to import manifests it creates, so I expected it to print an image hash.
Output of
buildah version
:Output of
cat /etc/*release
:Output of
uname -a
:The text was updated successfully, but these errors were encountered: