Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support for several tags per image

See original GitHub issue

Docker allows for tagging an image with several tags. is that doable with singularity/sregistry? sregistry could play an important role here because it would be the tag handler

for example

sregistry tag mso4sc/feelpp-toolbox:develop-v0.106.0-ubuntu-16.04 mso4sc/feelpp-toolbox:v106
sregistry tag mso4sc/feelpp-toolbox:develop-v0.106.0-ubuntu-16.04 mso4sc/feelpp-toolbox:latest

sregistry tag mso4sc/feelpp-toolbox:develop-v0.105.0-ubuntu-16.04 mso4sc/feelpp-toolbox:v105 
sregistry tag mso4sc/feelpp-toolbox:develop-v0.105.0-ubuntu-16.04 mso4sc/feelpp-toolbox:production

Encoding the tag in the filename when a pull is done is then a bad idea. A docker-like system would be better and an image is identified uniquely with a uuid.

/cc @trophime @victorsndvg

Issue Analytics

State:
Created 5 years ago
Comments:17 (13 by maintainers)

Top GitHub Comments

1reaction

victorsndvgcommented, Oct 15, 2018

@prudhomm , I think if you upload same image with several tags it’s going to be stored several times. @vsoch , I’m right?

I agree with Christophe, being able to assign several tags to the same image in the server side will help to better manage software lifecycles. I also think sregistry-cli could be the tool in charge of creating/assigning new tags to already stored images. sregistry-cli does not only works with the local repostory, in case of interacting with a sregistry server it allows to push, why no a tag or retag command?

0reactions

vsochcommented, Dec 11, 2019

There isn’t support for adding another tag to an existing image, but if you do upload the same ImageFile using the library client, it will share the same file:

https://github.com/singularityhub/sregistry/blob/master/shub/apps/library/views/images.py#L177

We can’t easily add this to the snippets above (upload from browser or with sregistry) because the nginx upload won’t give us a sha256 sum to ensure non-duplication. But hopefully over time more users will just use singularity to upload, and the other endpoints can be deprecated. Anyway, I’m closing the issue, because now uploading different tags for the same image file using the library client will not upload multiple images.