Proposal: Update labels
This is a follow-up issue to the closed PR #18958 that was only for containers. Now that networks, volumes, images and containers all support labels, we should probably rethink the idea (or not) of having a common way to update them, instead of only being able to update containers label and no others. /cc @icecrime @tiborvass @calavera @dnephin @ehazlett Pasting @tiborvass comment from https://github.com/docker/docker/issues/20356#issuecomment-194467286 below. --- Before going into technical details, I would like to find a good UX. I could come up with these 3 solutions, none of which I really like, but I prefer the 3rd one among these: 1. For each new object type (images, networks, volumes), add a new `update` subcommand to match the `docker update` that is for containers. Questions: is there anything else we would want to update on images networks and volumes? If so what? If we can't agree on those other things to update, then the problem with this solution is we would add a new subcommand just for labels. Moreover, for historical reasons `images` is not a subcommand the way `network` and `volume` are. So if we were to still go with this solution we should also choose between: 1.a) introduce `docker images update` subcommand OR 1.b) overload `docker update` the way we (unfortunately) overload `docker inspect` and accept: `docker update --label foo=bar $imageID`. 2. Overload `docker update` to non-container objects as well. Problem: how to deal with `docker update --me
Posted by vdemeester on Apr 1, 2016, 1:06 PM
Tags
Related issues
- I've been thinking about this question a lot recently and have asked my friends for their opinions.
- > There's really no reason console games of that era needed, or even could benefit from 6 cores First: One problem of the PS3 was that i...
- Remote session/task persistence: Detach, preserve, and reattach all active tasks, terminals, and extension processes in VS Code Remote
- Not only Eddie, their account control panels and site in general look like something from the 90s, and it seriously hampers their business.
- Signal don't want you to build 3rd party clients and integrations, they are another fully centralised product meant to capture and lock u...
- The page keeps crashing for me.
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
ux (Network)
I've been thinking about this question a lot recently and have asked my friends for their opinions.
> There's really no reason console games of that era needed, or even could benefit from 6 cores First: One problem of the PS3 was that i...
Remote session/task persistence: Detach, preserve, and reattach all active tasks, terminals, and extension processes in VS Code Remote
Not only Eddie, their account control panels and site in general look like something from the 90s, and it seriously hampers their business.
Signal don't want you to build 3rd party clients and integrations, they are another fully centralised product meant to capture and lock u...
The page keeps crashing for me.
Server-side pagination to make ArgoCD UI a rocket
[RFC] Zero-runtime CSS-in-JS implementation
Proposal: Update labels
This is a follow-up issue to the closed PR #18958 that was only for containers. Now that networks, volumes, images and containers all support labels, we should probably rethink the idea (or not) of having a common way to update them, instead of only being able to update containers label and no others. /cc @icecrime @tiborvass @calavera @dnephin @ehazlett Pasting @tiborvass comment from https://github.com/docker/docker/issues/20356#issuecomment-194467286 below. --- Before going into technical details, I would like to find a good UX. I could come up with these 3 solutions, none of which I really like, but I prefer the 3rd one among these: 1. For each new object type (images, networks, volumes), add a new `update` subcommand to match the `docker update` that is for containers. Questions: is there anything else we would want to update on images networks and volumes? If so what? If we can't agree on those other things to update, then the problem with this solution is we would add a new subcommand just for labels. Moreover, for historical reasons `images` is not a subcommand the way `network` and `volume` are. So if we were to still go with this solution we should also choose between: 1.a) introduce `docker images update` subcommand OR 1.b) overload `docker update` the way we (unfortunately) overload `docker inspect` and accept: `docker update --label foo=bar $imageID`. 2. Overload `docker update` to non-container objects as well. Problem: how to deal with `docker update --me
Comments (0)
No comments yet. Start the discussion.