-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
None
-
None
I'm using an funtoo based lxd host with a metro running inside a lxd container. metro container is based on Next Next Sandybridge 64bit 2023-01-19 image.
lxc image list +--------+--------------+--------+-----------------------------------------+--------------+-----------+----------+------------------------------+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCHITECTURE | TYPE | SIZE | UPLOAD DATE | +--------+--------------+--------+-----------------------------------------+--------------+-----------+----------+------------------------------+ | funtoo | 2d5c2afc81e6 | no | Next Next Sandybridge 64bit 2023-01-19 | x86_64 | CONTAINER | 506.39MB | Jan 28, 2023 at 4:23pm (UTC) | +--------+--------------+--------+-----------------------------------------+--------------+-----------+----------+------------------------------+
epro show lxd host
borisp@matrix ~ $ epro show
=== Enabled Profiles: ===
arch: x86-64bit
build: next
subarch: intel64-sandybridge
flavor: core
mix-ins: (not set)
=== Python kit: ===
branch: next
=== All inherited flavor from core flavor: ===
minimal (from core flavor)
epro show lxd container
borisp-metro-1 ~ # epro show
=== Enabled Profiles: ===
arch: x86-64bit
build: next
subarch: intel64-sandybridge
flavor: core
mix-ins: (not set)
=== Python kit: ===
branch: next
=== All inherited flavor from core flavor: ===
minimal (from core flavor)
During a metro build for generic64 fchrooting fails with the message '/dev/null' is not a device file
The persmissions of /dev/null inside and outside of lxd container are different
outside
crw-rw-rw- 1 root root 1, 3 Jan 28 22:33 /dev/null
inside
---------- 1 root root 19 Jan 29 08:08 /dev/null
I'm expecting fchrooting should work.
