Closed amitsaha closed 7 years ago
docker:
refers to images published on docker registry servers; in this context amitsaha/rootfs-1:latest
is read as a shorthand for docker.io/amitsaha/rootfs-1:latest
.
Accessing images managed locally by the Docker daemon is being worked on in containers/image, and accessible through https://github.com/mtrmac/skopeo/tree/docker-daemon , using a docker-daemon:
transport (e.g. docker-daemon:amitsaha/rootfs-1:latest
. This is known to be incomplete, nevertheless testing would be appreciated. A trivial smoke test seems to work.
@mtrmac awesome, going to test this now/soon ish and will report back! Thanks.
@mtrmac tested it just now, seems to be working great!
Thanks for testing, docker-daemon:
support is now merged in master.
docker-daemon:<image>
not docker-deamon://<image>
i hope this tip is helpful
docker-daemon:<image>
notdocker-deamon://<image>
i hope this tip is helpful
I'd consider making both variants work or documenting this idiosyncrasy / exception.
docker://
is the exception, really.
Hello, I know I can do this:
However, can I specify the source as a docker image which is only present locally? Trying it gives me:
If this is not yet available, is there any alternative to directly converting a docker image which is not in any supported registry to an OCI bundle? Thanks for any hints!