mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-10-21 21:37:38 +00:00
32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
####> This option file is used in:
|
|
####> podman build, podman-container.unit.5.md.in, create, farm build, pod clone, pod create, run
|
|
####> If file is edited, make sure the changes
|
|
####> are applicable to all of those.
|
|
<< if is_quadlet >>
|
|
### `AddDevice=host-device[:container-device][:permissions]`
|
|
<< else >>
|
|
#### **--device**=*host-device[:container-device][:permissions]*
|
|
<< endif >>
|
|
|
|
Add a host device to the <<container|pod>>. The format of this is
|
|
`HOST-DEVICE[:CONTAINER-DEVICE][:PERMISSIONS]`, where `HOST-DEVICE` is the path of
|
|
the device node on the host, `CONTAINER-DEVICE` is the path of the device node in
|
|
the container, and `PERMISSIONS` is a list of permissions combining 'r' for read,
|
|
'w' for write, and 'm' for mknod(2).
|
|
|
|
Example: **--device=/dev/sdc:/dev/xvdc:rwm**.
|
|
|
|
Note: if *host-device* is a symbolic link then it is resolved first.
|
|
The <<container|pod>> only stores the major and minor numbers of the host device.
|
|
|
|
Podman may load kernel modules required for using the specified
|
|
device. The devices that Podman loads modules for when necessary are:
|
|
/dev/fuse.
|
|
|
|
In rootless mode, the new device is bind mounted in the container from the host
|
|
rather than Podman creating it within the container space. Because the bind
|
|
mount retains its SELinux label on SELinux systems, the container can get
|
|
permission denied when accessing the mounted device. Modify SELinux settings to
|
|
allow containers to use all device labels via the following command:
|
|
|
|
$ sudo setsebool -P container_use_devices=true
|