| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Remove locks from volumes | Matthew Heon | 2019-02-21 |
| | | | | | | | | | | | | | | | | | | | | I was looking into why we have locks in volumes, and I'm fairly convinced they're unnecessary. We don't have a state whose accesses we need to guard with locks and syncs. The only real purpose for the lock was to prevent concurrent removal of the same volume. Looking at the code, concurrent removal ought to be fine with a bit of reordering - one or the other might fail, but we will successfully evict the volume from the state. Also, remove the 'prune' bool from RemoveVolume. None of our other API functions accept it, and it only served to toggle off more verbose error messages. Signed-off-by: Matthew Heon <matthew.heon@pm.me> | ||
| * | Remove runtime lockDir and add in-memory lock manager | Matthew Heon | 2019-01-04 |
| | | | | | | | | | | Remove runtime's lockDir as it is no longer needed after the lock rework. Add a trivial in-memory lock manager for unit testing Signed-off-by: Matthew Heon <matthew.heon@gmail.com> | ||
| * | Add "podman volume" command | umohnani8 | 2018-12-06 |
| Add support for podman volume and its subcommands. The commands supported are: podman volume create podman volume inspect podman volume ls podman volume rm podman volume prune This is a tool to manage volumes used by podman. For now it only handle named volumes, but eventually it will handle all volumes used by podman. Signed-off-by: umohnani8 <umohnani@redhat.com> | |||
 |
index : containers/podman.git | |
| forked from: https://github.com/containers/podman.git | User & |
| summaryrefslogtreecommitdiff |