-
Notifications
You must be signed in to change notification settings - Fork 447
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
Docker Buildx Does Not Seem To Respect Output Type Flag #2469
Comments
If you are using Docker tar layout can be made compatible with OCI tar. Exporting Docker tarball does not mean that there can not be
In order to export OCI tarball or Docker-compatible tarball directly from builder you need to use container/k8s/remote builder instance https://docs.docker.com/reference/cli/docker/buildx/create/ or containerd storage in your docker installation https://docs.docker.com/desktop/containerd/ If you want to control if the objects in the image use OCI or Docker mediatypes then the option for that is |
I think I possibly have the wrong terminology mixed up here then. I have a workflow that is compatible with the layout for Thanks for the speedy response!
Regarding the oci-mediatypes flag,
|
There's no breaking change. If you get file with |
I understand, but I am explicitly trying to get the unnested layout of the older versions. I am having trouble generating a tarball without the blobs folder on Docker v25+. |
That's not supported anymore. There was never any definition that this tarball needs to or is not allowed to contain directory named "blobs". The layout of the files is defined in |
Thank you @tonistiigi |
Discussed in #2458
Originally posted by justinba1010 May 14, 2024
It seems that the output type flag is ignored during exports. Not sure if I am using this incorrectly. It seems to be documented here:
https://docs.docker.com/build/exporters/oci-docker/
Goal: To build a tarball that has the docker layout instead of OCI, in v24 and below this was default OCI Compliance PR
Steps to recreate:
It would be expected that this tarball would have a docker image layout but it seems to be exported as an OCI image.
There seems to be documentation for other methods to skip the save step, but I have been unable to get those to work as well.
The text was updated successfully, but these errors were encountered: