...
Description of problem: lsblk does not work inside the container Version-Release number of selected component (if applicable): RHEL 8.6 Podman 4.1.1 How reproducible: Always Steps to Reproduce: 1. Start a container 2. Exec into the container 3. Run lsblk Actual results: lsblk lsblk: loop4435: failed to initialize sysfs handler lsblk: loop5532: failed to initialize sysfs handler lsblk: loop7727: failed to initialize sysfs handler lsblk: loop1709: failed to initialize sysfs handler lsblk: loop8824: failed to initialize sysfs handler lsblk: loop2806: failed to initialize sysfs handler lsblk: loop9921: failed to initialize sysfs handler lsblk: loop3903: failed to initialize sysfs handler . . Expected results: lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdy 65:128 0 80T 0 disk `-sdy3 65:131 0 80T 0 part sdam 66:96 0 80T 0 disk `-sdam3 66:99 0 80T 0 part sdbb 67:80 0 80T 0 disk `-sdbb3 67:83 0 80T 0 part sdf 8:80 0 80T 0 disk `-sdf3 8:83 0 80T 0 part sdau 66:224 0 80T 0 disk `-sdau3 66:227 0 80T 0 part . . . Additional info:
Unresolved
Click on a version to see all relevant bugs
Red Hat Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.