Skip to content
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

Explain single-platform limitation of docker export type #65

Merged
merged 1 commit into from May 6, 2019

Conversation

tiborvass
Copy link
Collaborator

Signed-off-by: Tibor Vass tibor@docker.com

Closes #59

Signed-off-by: Tibor Vass <tibor@docker.com>
@tonistiigi tonistiigi merged commit 361f52a into docker:master May 6, 2019
The `docker` export type writes the result image as an Docker image specification tarball https://github.com/moby/moby/blob/master/image/spec/v1.2.md on the client. Tarballs created by this exporter are also OCI compatible.
The `docker` export type writes the single-platform result image as a Docker image specification tarball https://github.com/moby/moby/blob/master/image/spec/v1.2.md on the client. Tarballs created by this exporter are also OCI compatible.

Currently, multi-platform images cannot be exported with the `docker` export type. The most common usecase for multi-platform images is to directly push to a registry (see [`registry`](#registry)).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's an assumption I do not agree to. You certainly want to run images locally before pushing. #59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Building images for multi-arch with --load parameter fails
3 participants