Skip to content

udev runtime directory unavailable in chroot

Created by: irminsul

Hi! I maintain a custom Arch installation script and noticed that it is broken since the release of v25 (8a561339).

Specifically, my script uses lsblk to get the PARTUUID of a block device like so:

lsblk -n -o PARTUUID /dev/nvme0n1p1

This fails inside an arch-chroot since lsblk needs the udev runtime data in /run/udev, which is unavailable because /run is just an empty tmpfs.

#15 (closed) mentions adding --make-private to the bind mount as an alternative to making /run a tmpfs. Is this a change you would consider, or should I rather stop using lsblk and get my UUIDs from /dev/disk/by-partuuid instead?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information