Running TopoLVM inside a privileged container frequently leads to mounting the entire /dev because TopoLVM depends on LVM2 and device-mapper, which create and update block device nodes dynamically under paths like /dev/mapper, /dev/dm-, and symlinks under /dev/disk/by-, and teams use privileged mode to broadly expose these updates inside the container for simplicity (RHEL LVM/Device-Mapper overview, Device Mapper + udev, Podman device access patterns).
- TopoLVM uses LVM/device-mapper, which materialize logical volumes as block devices under /dev/mapper and /dev/dm-