Matthew Heon 1ae410d19e 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>		2021-01-26 14:38:25 -05:00
..
completion.go	Rename AutocompletePortCommand func	2021-01-16 18:54:59 +01:00
create.go	Fix --arch and --os flags to work correctly	2021-01-25 14:58:24 -05:00
create_opts.go	Ensure the Volumes field in Compat Create is honored	2021-01-26 14:38:25 -05:00
createparse.go	Allow containers to --restart on-failure with --rm	2020-11-20 13:55:19 -05:00
default.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
diffChanges.go	Refactor podman to use c/common/pkg/report	2020-10-21 08:16:52 -07:00
netflags.go	shell completion for the network flag	2020-12-12 19:10:25 +01:00
ports.go	V2 enable ps tests	2020-04-29 15:51:37 -07:00
specgen.go	Set log driver for compatability containers	2021-01-20 13:07:31 -06:00
util.go	Remove some more excessive wrapping and stuttering	2020-11-17 09:19:22 -05:00
volumes.go	Reduce general binding binary size	2021-01-13 09:35:24 -06:00