-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Investigate if it's feasible to use local Docker or tar base image when building multi-platform images #2744
Comments
About local Docker daemon images: Note it is possible to pull an image to a Docker daemon even if the image platform doesn't match the platform running the daemon. (Of course, you can't run an image that doesn't match the machine platform.) However, I doubted a local Docker daemon could host something like a manifest list. Tried
It's not feasible to use a base image from a Docker daemon when configuring multiple |
About local tar images: Haven't looked into it, but I speculate that a tar image (either OCI or Docker) can easily contain multiple images. Worth taking a look. |
But for now, I think these are a low priority and we can just fail when attempting to use a local base image with multiple platforms configured. Should be done before we can enable multi-platform image building. |
added some local tar buildx image info on issue #2751 if relevant |
@tom-haines thanks for the info! |
Using an OCI image tarball or even directory as a base image would make a lot of sense. Related: #2173 |
It would also be of great help to output the built image into an oci directory structure instead of an oci tar, amending any existing index. |
No description provided.
The text was updated successfully, but these errors were encountered: