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
Tell us about your request
I would like to request that Docker images, tags and/or repositories as a whole can be flagged as immutable/ unoverwritable.
If a tag or repository is flagged as immutable then attempts to push a new image overwrite tags are denied
Which service(s) is this request for?
This change should be made to the DockerHub service.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
For the purposes of proper versioning, immutable images are required. Manifest Digests are a way of referencing an immutable image, however as they are generated after pushing, this makes referencing an image more complicated as its easier to reference the build version. After pushing an image with an associated tag, this tag can then be moved/overwritten at a later time and any service referencing an image using that tag is now subjected to the change.
Are you currently working around the issue?
We are currently use digests where we can and creating docker images with unique tags so that a tag should not be moved/overwritten.
The text was updated successfully, but these errors were encountered:
Tell us about your request
I would like to request that Docker images, tags and/or repositories as a whole can be flagged as immutable/ unoverwritable.
If a tag or repository is flagged as immutable then attempts to push a new image overwrite tags are denied
Which service(s) is this request for?
This change should be made to the DockerHub service.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
For the purposes of proper versioning, immutable images are required. Manifest Digests are a way of referencing an immutable image, however as they are generated after pushing, this makes referencing an image more complicated as its easier to reference the build version. After pushing an image with an associated tag, this tag can then be moved/overwritten at a later time and any service referencing an image using that tag is now subjected to the change.
Are you currently working around the issue?
We are currently use digests where we can and creating docker images with unique tags so that a tag should not be moved/overwritten.
The text was updated successfully, but these errors were encountered: