#lxc info --show-log local:GITLAB-ZA-1-H3-PRO-TER-ISA-ZA
Name: GITLAB-ZA-1-H3-PRO-TER-ISA-ZA
Remote: unix://
Architecture: x86_64
Created: 2021/11/09 12:17 UTC
Status: Stopped
Type: persistent
Profiles: default
Log:
lxc GITLAB-ZA-1-H3-PRO-TER-ISA-ZA 20211109121752.879 ERROR conf - conf.c:run_buffer:335 - Script exited with status 1
lxc GITLAB-ZA-1-H3-PRO-TER-ISA-ZA 20211109121752.879 ERROR start - start.c:lxc_init:859 - Failed to run lxc.hook.pre-start for container “GITLAB-ZA-1-H3-PRO-TER-ISA-ZA”
lxc GITLAB-ZA-1-H3-PRO-TER-ISA-ZA 20211109121752.880 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:833 - No such file or directory - Failed to receive the container state
At this stage the container refuses to start. Any idea what the cause could be?
Linux vm-host-03 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/issue
Ubuntu 18.04.6 LTS \n \l
The server has multiple containers running in production - it’s been running fine since we installed the server probably 2 years ago. The last “major” change was updating the packages with “apt upgrade” - we don’t get to add new containers on a daily basis so I only noticed this a few weeks ago and the last recorded change was running “apt upgrade”
Do I re-install apparmor? Will it pick up the profiles in order to function normally?
Since this is a production server, I’m hesitant to just try different things to get it back to a functional state…