You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Buildx imagetools create should allow reading content from oci-layout:// directories #1915
Essentially, it's becoming more common for users to want to export their images, and then push them later. There's a few legitimate reasons to want to do this:
Import the image into docker, and run validation tests on it before pushing
Manually verify image attestations like SBOMs, Provenance before pushing
Split out the build and push sections of a push to allow more manual control over flaky registries
The reason for using the oci-layout URL schema is just since BuildKit already uses this for overriding named contexts, so it would be good to stick with that.
Done in v0.33.0 (#3721): oci-layout://path[:tag|@digest] works as source and target for imagetools create and for inspect, and can be mixed with registry references. The reference pages still need a docs follow-up for it.
Activity
Oliniusz commentedon Sep 29, 2023
Another reason for the separation is that I would like to run those steps in parallel:
When the terraform apply has finished I can push the image to the newly created repository.
crazy-max commentedon Sep 3, 2026
Done in v0.33.0 (#3721):
oci-layout://path[:tag|@digest]works as source and target forimagetools createand forinspect, and can be mixed with registry references. The reference pages still need a docs follow-up for it.