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
It would be interesting if there was a command to sync metadata and images from a remote endpoint. Typically a remote endpoint may add new containers or tags and if user can have an option to sync and retrieve all metadata and maybe even download container from remote endpoint then user can do that in a few commands without having to know which container was uploaded.
Something like sregistry sync remote shub shahzebsiddiqui/eb-singularity will sync metadata from remote into sregistry.db. This may be problematic if you are using sregistry mv or any command to modify metadata afterwards.
The sync command can be used for other endpoints such as
sregistry sync remote dockerhub <collection>
The NGC repo may work if API is valid
sregistry sync remote ngc <collection>
This could be extended to the other endpoints sregistry support. There could be an option to also download the images but that could be tricky if you used sregistry mv.
The sync could be done on a container instance as well which can update the metadata and path to container. For instance if an image shahzebsiddiqui/eb-singularity:centos-7.3.1611 was pulled and moved in /tmp then the command
sregistry sync remote shub shahzebsiddiqui/eb-singularity:centos-7.3.1611 will fetch the metadata from remote and move the container to the path $SREGISTRY_STORAGE which is where image should have been pulled
The text was updated successfully, but these errors were encountered:
It would be interesting if there was a command to sync metadata and images from a remote endpoint. Typically a remote endpoint may add new containers or tags and if user can have an option to sync and retrieve all metadata and maybe even download container from remote endpoint then user can do that in a few commands without having to know which container was uploaded.
Something like
sregistry sync remote shub shahzebsiddiqui/eb-singularity
will sync metadata from remote into sregistry.db. This may be problematic if you are usingsregistry mv
or any command to modify metadata afterwards.The sync command can be used for other endpoints such as
sregistry sync remote dockerhub <collection>
The NGC repo may work if API is valid
sregistry sync remote ngc <collection>
This could be extended to the other endpoints sregistry support. There could be an option to also download the images but that could be tricky if you used
sregistry mv
.The sync could be done on a container instance as well which can update the metadata and path to container. For instance if an image
shahzebsiddiqui/eb-singularity:centos-7.3.1611
was pulled and moved in /tmp then the commandsregistry sync remote shub shahzebsiddiqui/eb-singularity:centos-7.3.1611
will fetch the metadata from remote and move the container to the path $SREGISTRY_STORAGE which is where image should have been pulledThe text was updated successfully, but these errors were encountered: