Containers management with Systemd

[Pedro Goofy]

Hello,

facing for some time now unexpected stops of containers, I have finally found that it is happening when needrestart tries to restart them with systemctl calls.
And indeed, it looks that systemctl start pve-container@xxx.service systematically fails with:

Mar 09 11:27:19 proxmox systemd[1]: Started PVE LXC Container: 102.
Mar 09 11:27:20 proxmox systemd[1]: pve-container@102.service: Main process exited, code=exited, status=1/FAILURE
Mar 09 11:27:20 proxmox systemd[1]: pve-container@102.service: Failed with result 'exit-code'.
Mar 09 11:27:20 proxmox systemd[1]: pve-container@102.service: Consumed 1.489s CPU time.

It happens with all the containers I have tested on an up to date Debian 11 + Proxmox 7.3-6 (pveversion attached). The debug mode (pre-container-debug) doesn't provide further information.

Any idea of the root cause?

 

[fabian]

you should definitely exclude pve-container@ from needrestart (and probably also some other things that should be left alone or reloaded instead of restarted).

 

[Pedro Goofy]

Thank you for your answer @fabian? I am going to follow your recommendation.