In the past, there were problems with systemd in LXC on systemd Debian Jessie (Proxmox VE 4), so that's why systemd is not in the default template. I don't know if the problems still persist. Try and check for yourself.
There is - of course - no how to to fix systemd. If there would be such a document, it would not exist because if would be fixed directly in Proxmox VE such that the problem would not arise.
There is - of course - no how to to fix systemd. If there would be such a document, it would not exist because if would be fixed directly in Proxmox VE such that the problem would not arise.
systemd on jessie is too old and don't support lxc. That's why it's disable in jessie template.
(Works fine with more recent ubuntu for example)
(Works fine with more recent ubuntu for example)
I did try just a few weeks ago and the problem does persist in the new image. I have an old lxc image I created a while ago (well converted from openvz) that I recently upgraded to jessie and it works great with systemd (it is a 32-bit and my new one is 64-bit if that makes a difference). I figured that if one worked maybe I could tweak the other to work.
You can use DAB (https://pve.proxmox.com/wiki/Debian_Appliance_Builder) to easily create your own Debian LXC template. I've put some example DAB templates on https://bitbucket.org/flybyte/dab-templates along with some information that should help you get started. In order to get systemd working with DAB you must check the instructions mentioned at https://bitbucket.org/snippets/flybyte/yjoMo.
As for the use of systemd in LXC, I've been using systemd for a couple of month now and never experienced any issues (Debian only). Not sure why the Proxmox team hardcoded the systemd exclusion in DAB but I'm sure they had their reasons. Luckily we can work around this.
As for the use of systemd in LXC, I've been using systemd for a couple of month now and never experienced any issues (Debian only). Not sure why the Proxmox team hardcoded the systemd exclusion in DAB but I'm sure they had their reasons. Luckily we can work around this.
Last edited:
I just realized that I've linked the wrong snippet for DAB/systemd. Please use https://bitbucket.org/snippets/flybyte/yjoMo instead.
Thanks, just followed your instructions and my new container appears to support systemd, no issues so far. Unfortunately, I will still need to recreate my entire server from the old container since I don't think I can modify an existing container to support systemd, but hey, at least the new one will work with systemd, so I won't have to rewrite a ton of my startup scripts.
