mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-11 11:25:45 +00:00
0d623914d0
Previously, when `podman run` encountered a volume mount without separate source and destination (e.g. `-v /run`) we would assume that both were the same - a bind mount of `/run` on the host to `/run` in the container. However, this does not match Docker's behavior - in Docker, this makes an anonymous named volume that will be mounted at `/run`. We already have (more limited) support for these anonymous volumes in the form of image volumes. Extend this support to allow it to be used with user-created volumes coming in from the `-v` flag. This change also affects how named volumes created by the container but given names are treated by `podman run --rm` and `podman rm -v`. Previously, they would be removed with the container in these cases, but this did not match Docker's behaviour. Docker only removed anonymous volumes. With this patch we move to that model as well; `podman run -v testvol:/test` will not have `testvol` survive the container being removed by `podman rm -v`. The sum total of these changes let us turn on volume removal in `--rm` by default. Fixes: #4276 Signed-off-by: Matthew Heon <matthew.heon@pm.me> |
||
|---|---|---|
| .. | ||
| shortcuts | ||
| checkpoint_restore.go | ||
| client.go | ||
| client_config.go | ||
| client_unix.go | ||
| client_windows.go | ||
| containers.go | ||
| containers_remote.go | ||
| errors.go | ||
| images.go | ||
| images_remote.go | ||
| info_remote.go | ||
| network.go | ||
| pods.go | ||
| pods_remote.go | ||
| runtime.go | ||
| runtime_remote.go | ||
| runtime_remote_supported.go | ||
| sigproxy_linux.go | ||
| terminal.go | ||
| terminal_linux.go | ||
| volumes_remote.go | ||