docker
Update Labels on Images, Containers, Volumes, Network...
hey @SvenDowideit could you add some notes on why you feel this matters/why now is the right time to do this please
It's about 5 years late - and is an important part of of making labels useful?
https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
This would be useful, yet it's never been responded to here.
Let me offer another simple use case: you or something creates a volume, without a label, with a name that is perhaps a long-random string. Soon you have many. When you do a docker volume ls, you have no idea what each volume is for--and a docker volume inspect shows no useful identifying info about the volume's intended purpose.
So you'd like to give the volume a label, as a form of metadata....only you can't, because the only provision to label a volume is when it's created.
It certainly seems it would be straightforward to provide for labeling it after creation, whether with a docker volume label command, or perhaps some sort of docker update command.
As a mere users of Docker, it's not clear from the outside how difficult it would be to even try to propose a code change to enable this, if one were game to try. As this is one of the places where this idea is being discussed, it seemed worth debating it first.
The lack of interest here seems to suggest either that there's difficulty not obvious to we who are asking, or there a lack of appreciation of the problem. I have tried to help with the latter. :-) Perhaps others will chime in, for or against.
Any updates on the feat? There are tons of use cases listed here https://github.com/moby/moby/issues/21721
