search

whiskerz007 / proxmox_hassio_lxc

MIT License
208 stars 83 forks source link

Lxc only starts when commenting lxc.hook.pre-start after upgrading to proxmox 7 #49

Open tomcassi opened 2 years ago

tomcassi commented 2 years ago

Hi, after upgrading to proxmox 7, the home assistant container would only start if I comment the lxc.hook.pre-start line in the config file for the container.

The full line is lxc.hook.pre-start: sh -ec 'for module in aufs overlay; do modinfo $module; $(lsmod | grep -Fq $module) || modprobe $module; done;'

home assistant seems to work fine with this line commented. Should I be ok running it this way?

hockey6611 commented 2 years ago

@Tom-ST have still been running your home assistant lxc with the lxc.hook.pre-start commented out? I have just upgraded from proxmox 6.4 to 7.2 and ran into this issue. I commented out this line in the config and everything seems to work (so far).

in #45, @fragtion had the same error and was able to solve it with further updates. I was not able to accomplish this.

tomcassi commented 2 years ago

@hockey6611 Sorry I won’t be able to answer, because currently I’m running home assistant as a VM in proxmox, which seems to work fine. Although I don’t remember why I chose to switch from lxc to VM.

hockey6611 commented 2 years ago

@hockey6611 Sorry I won’t be able to answer, because currently I’m running home assistant as a VM in proxmox, which seems to work fine. Although I don’t remember why I chose to switch from lxc to VM.

Thank you for the reply. That certainly is the sensible (and officially supported choice). I like the resource efficiency of the containers, even if it is a bit of a pain sometimes. Though, it is reassuring that it is theoretically easy to move to a VM if using LXC's do completely break in the future.