aboutsummaryrefslogtreecommitdiff
path: root/pkg/lookup
diff options
context:
space:
mode:
authorMatthew Heon <matthew.heon@pm.me>2019-05-21 10:16:02 -0400
committerMatthew Heon <matthew.heon@pm.me>2019-05-28 14:00:54 -0400
commitcd393d0d683c9407388dfc4c50a4089ea7106c4c (patch)
treeb42f6fcff7b25c4684435e957dcfc5d644675505 /pkg/lookup
parent7210727e205c333af9a2d0ed0bb66adcf92a6369 (diff)
downloadpodman-cd393d0d683c9407388dfc4c50a4089ea7106c4c.tar.gz
podman-cd393d0d683c9407388dfc4c50a4089ea7106c4c.tar.bz2
podman-cd393d0d683c9407388dfc4c50a4089ea7106c4c.zip
When superceding mounts, check for opposite types
When we supercede low-priority mounts and volumes (image volumes, and volumes sourced from --volumes-from) with higher-priority ones (the --volume and --mount flags), we always replaced lower-priority mounts of the same type (e.g. a user mount to /tmp/test1 would supercede a volumes-from mount to the same destination). However, we did not supercede the opposite type - a named volume from image volumes at /tmp/test1 would be allowed to remain and create a conflict, preventing container creation. Solve this by destroying opposite types before merging (we can't do it in the same loop, as then named volumes, which go second, might trample changes made by mounts). Fixes #3174 Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Diffstat (limited to 'pkg/lookup')
0 files changed, 0 insertions, 0 deletions