podman-volume-create - Man Page

Specify the volume driver name (default local). There are two drivers supported by Podman itself: local and image.

The local driver uses a directory on disk as the backend by default, but can also use the mount(8) command to mount a filesystem as the volume if --opt is specified.

The image driver uses an image as the backing store of for the volume. An overlay filesystem is created, which allows changes to the volume to be committed as a new layer on top of the image.

Using a value other than local or image, Podman attempts to create the volume using a volume plugin with the given name. Such plugins must be defined in the volume_plugins section of the containers.conf(5) configuration file.

Print usage statement

Don't fail if the named volume already exists, instead just print the name. Note that the new options are not applied to the existing volume.

Set metadata for a volume (e.g., --label mykey=value).

Set driver specific options. For the default driver, local, this allows a volume to be configured to mount a filesystem on the host.

For the local driver the following options are supported: type, device, o, and [no]copy.

• The type option sets the type of the filesystem to be mounted, and is equivalent to the -t flag to mount(8).
• The device option sets the device to be mounted, and is equivalent to the device argument to mount(8).
• The copy option enables copying files from the container image path where the mount is created to the newly created volume on the first run.  copy is the default.

The o option sets options for the mount, and is equivalent to the filesystem options (also -o) passed to mount(8) with the following exceptions:

• The o option supports uid and gid options to set the UID and GID of the created volume that are not normally supported by mount(8).
• The o option supports the size option to set the maximum size of the created volume, the inodes option to set the maximum number of inodes for the volume, and noquota to completely disable quota support even for tracking of disk usage. The size option is supported on the "tmpfs" and "xfs[note]" file systems. The inodes option is supported on the "xfs[note]" file systems. Note: xfs filesystems must be mounted with the prjquota flag described in the xfs_quota(8) man page. Podman will throw an error if they're not.
• The o option supports using volume options other than the UID/GID options with the local driver and requires root privileges.
• The o options supports the timeout option which allows users to set a driver specific timeout in seconds before volume creation fails. For example, --opt=o=timeout=10 sets a driver timeout of 10 seconds.

Note Do not confuse the --opt,-o create option with the -o mount option.  For example, with podman volume create, use -o=o=uid=1000 not -o=uid=1000.

For the image driver, the only supported option is image, which specifies the image the volume is based on. This option is mandatory when using the image driver.

When not using the local and image drivers, the given options are passed directly to the volume plugin. In this case, supported options are dictated by the plugin in question, not Podman.

The above example works because the volume is mounted as the host user and inside the container root is mapped to the user in the host.

If the mount is accessed by a different user inside the container, a "Permission denied" error will be raised.

$ podman run --user bin:bin -v s3fs-fuse-volume:/s3:z,U --rm -it fedora:latest
$ ls /s3
# ls: /s3: Permission denied

In FUSE-land, mounts are protected for the user who mounted them; specify the allow_other mount option if other users need access. > Note: This will remove the normal fuse security measures on the mount point, after which, the normal filesystem permissions will have to protect it

$ podman volume create s3fs-fuse-other-volume -o type=fuse.s3fs -o device=bucket:/prefix -o o=allow_other,use_xattr,endpoint=aq-central-1
$ podman run --user bin:bin -v s3fs-fuse-volume:/s3:z,U --rm -it fedora:latest
$ ls /s3

s3fs will fail to mount if the prefix does not exist in the bucket.

Create a s3-directory by putting an empty object at the desired prefix/ key

$ aws s3api put-object --bucket bucket --key prefix/

If performance is the priority, please check out the more performant goofys.