summaryrefslogtreecommitdiff
path: root/test/e2e/trust_test.go
diff options
context:
space:
mode:
authorMatthew Heon <mheon@redhat.com>2021-01-19 13:41:50 -0500
committerMatthew Heon <matthew.heon@pm.me>2021-01-29 15:22:57 -0500
commitbb88db783c1756291e8047a1a7ffd214477f7f9b (patch)
treee016e577875ce1e18600e62774c48583626a4300 /test/e2e/trust_test.go
parent5747fd71c98238d42cf9cd307fdf4d59747a6e1d (diff)
downloadpodman-bb88db783c1756291e8047a1a7ffd214477f7f9b.tar.gz
podman-bb88db783c1756291e8047a1a7ffd214477f7f9b.tar.bz2
podman-bb88db783c1756291e8047a1a7ffd214477f7f9b.zip
Ensure the Volumes field in Compat Create is honored
Docker has, for unclear reasons, three separate fields in their Create Container struct in which volumes can be placed. Right now we support two of those - Binds and Mounts, which (roughly) correspond to `-v` and `--mount` respectively. Unfortunately, we did not support the third, `Volumes`, which is used for anonymous named volumes created by `-v` (e.g. `-v /test`). It seems that volumes listed here are *not* included in the remaining two from my investigation, so it should be safe to just append them into our handling of the `Binds` (`-v`) field. Fixes #8649 Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'test/e2e/trust_test.go')
0 files changed, 0 insertions, 0 deletions