{"action":"created","issue":{"url":"https://api.github.com/repos/singularityhub/sregistry/issues/101","repository_url":"https://api.github.com/repos/singularityhub/sregistry","labels_url":"https://api.github.com/repos/singularityhub/sregistry/issues/101/labels{/name}","comments_url":"https://api.github.com/repos/singularityhub/sregistry/issues/101/comments","events_url":"https://api.github.com/repos/singularityhub/sregistry/issues/101/events","html_url":"https://github.com/singularityhub/sregistry/issues/101","id":301094608,"number":101,"title":"Assign multiple tags to a single image or rename tag","user":{"login":"victorsndvg","id":6474985,"avatar_url":"https://avatars3.githubusercontent.com/u/6474985?v=4","gravatar_id":"","url":"https://api.github.com/users/victorsndvg","html_url":"https://github.com/victorsndvg","followers_url":"https://api.github.com/users/victorsndvg/followers","following_url":"https://api.github.com/users/victorsndvg/following{/other_user}","gists_url":"https://api.github.com/users/victorsndvg/gists{/gist_id}","starred_url":"https://api.github.com/users/victorsndvg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/victorsndvg/subscriptions","organizations_url":"https://api.github.com/users/victorsndvg/orgs","repos_url":"https://api.github.com/users/victorsndvg/repos","events_url":"https://api.github.com/users/victorsndvg/events{/privacy}","received_events_url":"https://api.github.com/users/victorsndvg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-02-28T16:36:31Z","updated_at":"2018-03-01T14:51:35Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Hi @vsoch,\r\n\r\nI have a new request. I would like to have several tags for the same image. Think in something like the common `latest` tag.\r\n\r\nSome possible use cases are:\r\n  - the last published version of my software is 1.0.0. There is a new release 1.1.0. The API has not changed. I want my users not to be necessarily aware of this change and I provide a common tag (`version_1`) to access all version 1.X.X of my software. \r\n  - I'm creating my images in a CI process. The image is created and then tested. Sregistry stores the temporal image. The image is pulled and tested. If fails the image is removed. If succeeds the tag is renamed or a new tag is added to the image.\r\n\r\nIn my opinion, having a tag acting as symlink and pointing to a particular image, or even being able to rename a tage could increase the flexibility of the workflows while working with sregistry.\r\n\r\nWhat do you think?"},"comment":{"url":"https://api.github.com/repos/singularityhub/sregistry/issues/comments/369615828","html_url":"https://github.com/singularityhub/sregistry/issues/101#issuecomment-369615828","issue_url":"https://api.github.com/repos/singularityhub/sregistry/issues/101","id":369615828,"user":{"login":"victorsndvg","id":6474985,"avatar_url":"https://avatars3.githubusercontent.com/u/6474985?v=4","gravatar_id":"","url":"https://api.github.com/users/victorsndvg","html_url":"https://github.com/victorsndvg","followers_url":"https://api.github.com/users/victorsndvg/followers","following_url":"https://api.github.com/users/victorsndvg/following{/other_user}","gists_url":"https://api.github.com/users/victorsndvg/gists{/gist_id}","starred_url":"https://api.github.com/users/victorsndvg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/victorsndvg/subscriptions","organizations_url":"https://api.github.com/users/victorsndvg/orgs","repos_url":"https://api.github.com/users/victorsndvg/repos","events_url":"https://api.github.com/users/victorsndvg/events{/privacy}","received_events_url":"https://api.github.com/users/victorsndvg/received_events","type":"User","site_admin":false},"created_at":"2018-03-01T14:51:35Z","updated_at":"2018-03-01T14:51:35Z","author_association":"CONTRIBUTOR","body":"It doesn't solve my expectations. If I want to publish the same image through SRegistry with 2 different tags:\r\n```\r\n$ sregistry push --name collection/container --tag tag1 image.simg\r\n$ sregistry push --name collection/container --tag tag2 image.simg\r\n```\r\n\r\nI will have this in SRegistry:\r\n```\r\ncollection/container:tag1\r\ncollection/container:tag2\r\n```\r\n\r\nStoring exactly the same image more than 1 times is undesirable from the point of view of the storage. I think we should avoid or, at least, provide an alternative to avoid duplicated images in the server side\r\n\r\nHave you planned to deal with this?\r\n\r\nIf not feel free to close this thread"}}
{"actor":{"display_login":"victorsndvg"}}