FS#58329 - [arch-install-scripts] Does pacstrap need access to /dev?
Attached to Project:
Arch Linux
Opened by Philip Abernethy (Chais) - Tuesday, 24 April 2018, 00:21 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 18 September 2023, 17:53 GMT
Opened by Philip Abernethy (Chais) - Tuesday, 24 April 2018, 00:21 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 18 September 2023, 17:53 GMT
|
Details
Description:
I'm tinkering with lxc and noticed that pacstrap fails in an unprivileged container. Digging a little deeper I narrowed it down to this line: ``` chroot_add_mount udev "$1/dev" -t devtmpfs -o mode=0755,nosuid ``` I don't see why a fully initialised devfs is necessary for installing packages. Useful devs like null or urandom could either be used from the host or initialised separately, but I'd be surprised and suspicious if a package required direct access to, say, a block device during installation. Am I missing something here? Or was this just the simplest solution and nobody tried building a chroot in an unprivileged lxc, yet? |
This task depends upon
Closed by Jelle van der Waa (jelly)
Monday, 18 September 2023, 17:53 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/a rch-install-scripts/issues/64
Monday, 18 September 2023, 17:53 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/a rch-install-scripts/issues/64
Things like GRUB certainly need access to real devices, but is GRUB useful in a chroot environment?