-
Notifications
You must be signed in to change notification settings - Fork 180
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
Pushing an image manifest JSON [feature request] #238
Comments
It looks to me as if you are trying to use ORAS to build container images, without any other artifacts involved. Please, correct me if I'm wrong. I don't think ORAS is supposed to be used for this purpose... Have you considered using umoci? BTW, which version of ORAS are you using? I've used v0.10.0 and v0.11.0 and no option |
I'm pushing artifacts that happen to be tarballs, and I've added OCI container image metadata to make them look like a container image, even though they're not really..
I didn't know about
Sorry, I wasn't clear. The I have constructed a https://github.com/opencontainers/image-spec/blob/master/manifest.md#image-manifest |
Hi @sjackman, |
https://github.com/containers/skopeo worked for me! Thanks, Steve. You can close this issue. I now use |
Manifest push discussed in #459 should cover this. |
Covered by #472 |
Addressed and closed by #494 |
I'd like to prepare an image manifest JSON myself, and push it to a specified
name:tag
. For example:All of the individual layers have already been pushed.
The text was updated successfully, but these errors were encountered: