Tetrov
(JB)
January 19, 2026, 8:34pm
1
Sometimes my OCI container fails on start and I want to know why.
incus info --show-log netbird-coturn
is not that useful, or what I missing?
lxc netbird-coturn 20260119202521.956 WARN cgfsng - ../src/lxc/cgroups/cgfsng.c:__cgroup_tree_create:747 - File exists - Creating the final cgroup 10(lxc.monitor.netbird-coturn) failed
lxc netbird-coturn 20260119202521.956 WARN cgfsng - ../src/lxc/cgroups/cgfsng.c:cgroup_tree_create:807 - File exists - Failed to create monitor cgroup 10(lxc.monitor.netbird-coturn)
lxc netbird-coturn 20260119202521.969 ERROR utils - ../src/lxc/utils.c:safe_mount:1334 - Invalid argument - Failed to mount "none" onto "/opt/incus/lib/lxc/rootfs/run"
Thank you.
stgraber
(Stéphane Graber)
January 19, 2026, 9:47pm
2
I don’t think that any of that is actually fatal.
Does incus console --show-log netbird-coturn show something more useful?
Tetrov
(JB)
January 20, 2026, 8:19am
3
The entrypoint called script which didn’t exist. I had to debug it within the container. So I wondered if there is some way to see the actual errors if container fails to start.
incus console --show-log netbird-coturn is empty for this one.
osch
January 20, 2026, 9:33am
4
Sometimes starting the container like this:
incus start netbird-coturn –console prints interesting details too.
In some cases the containers fails to early to print anything into the logs.
1 Like
cstby
January 21, 2026, 2:03am
5
You could try looking at /var/log/incus/netbird-coturn/console.log.