Closed x32767 closed 1 month ago
Pretty odd.
Can you show incus console --show-log square-crayfish
and incus info --show-log square-crayfish
?
Thank you for response.
test@debian:~$ incus console --show-log square-crayfish
Failed to mount tmpfs at /dev/shm: Invalid argument
Failed to mount tmpfs at /run: Invalid argument
Failed to mount tmpfs at /run/lock: Invalid argument
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
test@debian:~$ incus info --show-log square-crayfish
Name: square-crayfish
Status: STOPPED
Type: container
Architecture: aarch64
Created: 2024/08/24 20:53 CDT
Last Used: 2024/09/01 13:46 CDT
Log:
lxc square-crayfish 20240901184641.129 WARN idmap_utils - ../src/lxc/idmap_utils.c:lxc_map_ids:165 - newuidmap binary is missing
lxc square-crayfish 20240901184641.129 WARN idmap_utils - ../src/lxc/idmap_utils.c:lxc_map_ids:171 - newgidmap binary is missing
lxc square-crayfish 20240901184641.131 WARN idmap_utils - ../src/lxc/idmap_utils.c:lxc_map_ids:165 - newuidmap binary is missing
lxc square-crayfish 20240901184641.131 WARN idmap_utils - ../src/lxc/idmap_utils.c:lxc_map_ids:171 - newgidmap binary is missing
I then tried to fix it with apt install rootlesskit
, but after that, it still cannot start.
test@debian:~$ incus start square-crayfish
test@debian:~$ incus list
+-----------------+---------+------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+-----------------+---------+------+------+-----------+-----------+
| square-crayfish | STOPPED | | | CONTAINER | 0 |
+-----------------+---------+------+------+-----------+-----------+
test@debian:~$ incus info --show-log square-crayfish
Name: square-crayfish
Status: STOPPED
Type: container
Architecture: aarch64
Created: 2024/08/24 20:53 CDT
Last Used: 2024/09/01 13:50 CDT
Log:
test@debian:~$ incus console --show-log square-crayfish
Failed to mount tmpfs at /dev/shm: Invalid argument
Failed to mount tmpfs at /run: Invalid argument
Failed to mount tmpfs at /run/lock: Invalid argument
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
Interesting, I'll try it again on aarch64 here. I wonder if that's related to the new mount API somehow.
Reproduced the issue here
Sent a fix for this
Required information
The output of "incus info" or if that fails:
Incus version:
Storage backend in use:
dir
Issue description
Container in above environment cannot start after setting
security.syscalls.intercept.mount: "true"
to config.Firstly I was trying to install Waydroid headlessly into an Incus container inside a libvirt VM on Raspberry Pi OS Lite. Later I encounter this issue when trying to enable mount capability for the container. More info.
Later I found even for brand new VM, this issue still occurs.
Steps to reproduce
Information to attach
incus monitor --pretty
log when starting the container. It seems the container started and then quickly stopped.Here is the
incus monitor --pretty
log if I didn't addsecurity.syscalls.intercept.mount: "true"
.