Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't start Hassio container after pve-kernel-5.11 #116

Open
LarsNorgaard opened this issue Jun 14, 2021 · 0 comments
Open

Can't start Hassio container after pve-kernel-5.11 #116

LarsNorgaard opened this issue Jun 14, 2021 · 0 comments

Comments

@LarsNorgaard
Copy link

Hi,

after upgrading the kernel the CT homeassistant instance won't start anymore.

run_buffer: 314 Script exited with status 1 lxc_init: 798 Failed to run lxc.hook.pre-start for container "100" __lxc_start: 1945 Failed to initialize container "100" TASK ERROR: startup for container '100' failed

Detailed log says something about missing Aufs?

lxc-start 100 20210614194937.768 INFO     lsm - lsm/lsm.c:lsm_init:40 - Initialized LSM security driver AppArmor
lxc-start 100 20210614194937.768 INFO     conf - conf.c:run_script_argv:331 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
lxc-start 100 20210614194939.979 INFO     conf - conf.c:run_script_argv:331 - Executing script "sh -ec 'for module in aufs overlay; do modinfo $module; $(lsmod | grep -Fq $module) || modprobe $module; done;'" for container "100", config$
lxc-start 100 20210614194939.991 DEBUG    conf - conf.c:run_buffer:303 - Script exec sh -ec 'for module in aufs overlay; do modinfo $module; $(lsmod | grep -Fq $module) || modprobe $module; done;' 100 lxc pre-start produced output: modi$
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant