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
skopeo "is a command line utility that performs various operations on container images and image repositories". It has a copy command to "copy container images between various storage mechanisms".
Here's an example that copies a container from DockerHub to a local OCI-layout directory.
Edit: Taking a slightly closer look I'm not sure, so s/should/might/.
This may help with podman integration (Support 'podman' #89) since IIUC podman still works from a local store of containers and we'd need a similar save/load adapter.
Similar to the command above, we should be able to copy from the dataset directory to the local daemon storage.
One of the motivations of the docker adapter is lack of singularity support on Windows, so we probably wouldn't be able to completely replace the current approach with skopeo, which I don't think has any Windows support. And docker load doesn't support the OCI layout (there's a draft PR from February),
skopeo would be an optional dependency.
skopeo isn't yet packaged for Debian.
The text was updated successfully, but these errors were encountered:
Interesting! Google says that singularity 3.1.0 announced full compliance with oci ... May be indeed we could just store oci and compose necessary to the actual solution (docker, singularity) images "on the fly".
skopeo "is a command line utility that performs various operations on container images and image repositories". It has a
copy
command to "copy container images between various storage mechanisms".Here's an example that copies a container from DockerHub to a local OCI-layout directory.
I need to look into skopeo more, but here are some things to consider:
The above command works without docker installed or the daemon running.
Like the
docker save
output, the OCI layout can be nicely stored and de-duplicated as annex content in the dataset.The above layout should still work with a solution to attach URLs to individual layers (Provide URLs to individual docker image layers #98).
Edit: Taking a slightly closer look I'm not sure, so s/should/might/.
This may help with podman integration (Support 'podman' #89) since IIUC podman still works from a local store of containers and we'd need a similar save/load adapter.
Similar to the command above, we should be able to copy from the dataset directory to the local daemon storage.
One of the motivations of the docker adapter is lack of singularity support on Windows, so we probably wouldn't be able to completely replace the current approach with skopeo, which I don't think has any Windows support. And
docker load
doesn't support the OCI layout (there's a draft PR from February),skopeo would be an optional dependency.
skopeo isn't yet packaged for Debian.
The text was updated successfully, but these errors were encountered: