summaryrefslogtreecommitdiff
path: root/docs/source/markdown/podman-search.1.md
diff options
context:
space:
mode:
authorAditya Rajan <arajan@redhat.com>2021-12-28 16:02:25 +0530
committerAditya R <arajan@redhat.com>2022-01-28 13:10:15 +0530
commite64e6500d3a3bdbb2d3c9faa5e2d9d845f120b17 (patch)
tree21f9548d8b1c880359a44a2c2357d31a0452f442 /docs/source/markdown/podman-search.1.md
parent5b01dab618fc287df4e6c41fa88c4a64d31fa3f3 (diff)
downloadpodman-e64e6500d3a3bdbb2d3c9faa5e2d9d845f120b17.tar.gz
podman-e64e6500d3a3bdbb2d3c9faa5e2d9d845f120b17.tar.bz2
podman-e64e6500d3a3bdbb2d3c9faa5e2d9d845f120b17.zip
volume: add support for non-volatile upperdir,workdir for overlay volumes
Often users want their overlayed volumes to be `non-volatile` in nature that means that same `upper` dir can be re-used by one or more containers but overall of nature of volumes still have to be `overlay` so work done is still on a overlay not on the actual volume. Following PR adds support for more advanced options i.e custom `workdir` and `upperdir` for overlayed volumes. So that users can re-use `workdir` and `upperdir` across new containers as well. Usage ```console $ podman run -it -v myvol:/data:O,upperdir=/path/persistant/upper,workdir=/path/persistant/work alpine sh ``` Signed-off-by: Aditya R <arajan@redhat.com>
Diffstat (limited to 'docs/source/markdown/podman-search.1.md')
0 files changed, 0 insertions, 0 deletions