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

Cannot import docker archive with more then one image #556

Closed
chilicat opened this Issue Oct 2, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@chilicat

chilicat commented Oct 2, 2018

It seems like that skopeo does not support to copy a docker-archive with more than one image to a registry

Example:

docker pull busybox:latest 
docker pull  alpine:latest
docker save alpine:latest busybox:latest -o test.tar

skopeo  copy docker-archive:./test.tar docker://my-registry:5000

FATA[0000] Error determining manifest MIME type for docker-archive:./test.tar: Unexpected tar manifest.json: expected 1 item, got 2 

It would be great to support that use-case.

@mtrmac

This comment has been minimized.

Show comment
Hide comment
@mtrmac

mtrmac Oct 3, 2018

Collaborator

Right; you can write docker-archive:./test.tar:alpine:latest, but that currently only results in a warning

docker-archive: references are not supported for sources (ignoring)

Collaborator

mtrmac commented Oct 3, 2018

Right; you can write docker-archive:./test.tar:alpine:latest, but that currently only results in a warning

docker-archive: references are not supported for sources (ignoring)

@chilicat

This comment has been minimized.

Show comment
Hide comment
@chilicat

chilicat Oct 3, 2018

What I'm actually looking for is to import all images with one command. The deployment process I'm implementing does not know about the images in the archive.

chilicat commented Oct 3, 2018

What I'm actually looking for is to import all images with one command. The deployment process I'm implementing does not know about the images in the archive.

@mtrmac

This comment has been minimized.

Show comment
Hide comment
@mtrmac

mtrmac Oct 3, 2018

Collaborator

skopeo copy fundamentally works one image at a time; containers/image does not have a “repository of images” abstraction. #524 is somewhat moving in that direction, but it’s non-trivial.

A single container image is more or less everywhere the same kind of thing with the same semantics, but groups of images have very different semantics (gzipped archives where there is very high cost to setting them up; Docker repositories where some images are only reachable by digests which can’t be listed; arbitrary subdirectory structures; the very complex OCI nested indexes with quite unclear semantics) and it’s very unclear whether hiding all of that behind a single abstraction is viable.

Collaborator

mtrmac commented Oct 3, 2018

skopeo copy fundamentally works one image at a time; containers/image does not have a “repository of images” abstraction. #524 is somewhat moving in that direction, but it’s non-trivial.

A single container image is more or less everywhere the same kind of thing with the same semantics, but groups of images have very different semantics (gzipped archives where there is very high cost to setting them up; Docker repositories where some images are only reachable by digests which can’t be listed; arbitrary subdirectory structures; the very complex OCI nested indexes with quite unclear semantics) and it’s very unclear whether hiding all of that behind a single abstraction is viable.

@mtrmac mtrmac closed this Oct 3, 2018

@mtrmac mtrmac reopened this Oct 3, 2018

@chilicat

This comment has been minimized.

Show comment
Hide comment
@chilicat

chilicat Oct 3, 2018

Yes, that looks like the feature I'm looking for. I will close the issue.
Thank you for your response.

chilicat commented Oct 3, 2018

Yes, that looks like the feature I'm looking for. I will close the issue.
Thank you for your response.

@chilicat chilicat closed this Oct 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment