'lxc info --show-log' has unclear documentation and possibly does not work properly

Running Arch and AUR/LXD.

pacman -Q lxd lxcfs        
lxd 4.19-1
lxcfs 4.0.11-1
lxc info --show-log --help 
     --show-log    Show the instance's last 100 log lines?
# lxc info --show-log guard
Name: guard
Type: container
Architecture: x86_64
Created: 2021/10/01 14:35 CEST
Last Used: 2021/10/22 19:36 CEST


lxc guard 20211022173651.121 ERROR    start - start.c:core_scheduling:1572 - No such device - Failed to create new core scheduling domain
lxc guard 20211022173651.124 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:867 - Received container state "ABORTING" instead of "RUNNING"
lxc guard 20211022173651.149 ERROR    start - start.c:__lxc_start:2068 - Failed to spawn container "guard"
lxc guard 20211022173651.150 WARN     start - start.c:lxc_abort:1038 - No such process - Failed to send SIGKILL via pidfd 17 for process 2802
lxc 20211022173656.592 ERROR    af_unix - af_unix.c:lxc_abstract_unix_recv_fds_iov:218 - Connection reset by peer - Failed to receive response
lxc 20211022173656.594 ERROR    commands - commands.c:lxc_cmd_rsp_recv_fds:127 - Failed to receive file descriptors

Actually running the command gets me only 6 lines on a container that keeps failing.

Does the command actually give me the full log?
Does the command only give log for the latest instance start and not for all launch attempts?
Why is there a question mark in the --help line?

Also, unsure why trying to start any containers results in this error, LXD works in seemingly same configuration on another one of my servers and the container seems to be all there in /var/lib/lxd/storage-pools/default/containers/guard

@brauner looks like a core scheduling related regression, can you take a look?

I receive a similar error.

Downgrading to LXC 4.0.10 helps.

Report on Github is here: https://github.com/lxc/lxd/issues/9419

There also seems to be a fix in the making: https://github.com/lxc/lxc/pull/4010

The container startup issue was fixed in Arch’s lxc 1:4.0.11-2 which carries the extra patch

I am afraid the fix doesn’t work when using Archlinux’s LTS kernel :frowning:

Please see my report.

I understand that a fix is in the making for LTS kernel, so for the moment, we should downgrade to lxc 4.0.10-2 until next iteration of the lxc 4.0.11 package (most probably 4.0.11-3).

1 Like