RATIONALE The default proxmox debian 8 template, debian-8.0-standard_8.4-1_amd64.tar.gz 20-Apr-2016 12:16, from http://download.proxmox.com/images/system/ , ships with sysv. (See “If I remember correctly, there is a problem with nested systemd. Therefore the Debian 8 template ships with sysvinit instead of systemd. #2 LnxBil, Jul 31, 2016 “ https://forum.proxmox.com/threads/systemd-not-starting-on-lxc.28447/#post-143593 ). To test your current lxc run “ ps -p 1 -o comm=” . If returns init, is sysv. If returns systemd, it’s obvious. On the other hand, the problem is solved now for Debian LXC : “ The versions in both jessie and stretch support systemd in the container just fine for Debian guests.” https://wiki.debian.org/LXC#Incompatibility_with_systemd This is an important feature, I guess some applications rely on systemd. For my particular use case, installing http://www.ispconfig.org/ works with sysv, but fails to generate vhost files. My workaround is to copy manually the vhost.err generated files to the genuine vhost file and restart apache2. Furthermore, I consider that debian 8 template is the most important lxc template for Proxmox. Since host system is Debian8 with Ubuntu based kernel, you should be always safe if the container OS is also Debian8 ( see https://forum.proxmox.com/threads/p...stability-after-host-os-kernel-upgrade.29573/ ). Btw, Tom https://forum.proxmox.com/members/tom.193/ is runnig his production LXCs with Debian. There’s 2 workarounds at the moment, none of them working yet. WORKAROUND 1 - Using standard LXC images Following Dietmar's suggestion "You can also use standard LXC images: https://images.linuxcontainers.org/images/ " via https://forum.proxmox.com/threads/l...common-linux-distributions.25947/#post-130172 I have used https://uk.images.linuxcontainers.org/images/debian/jessie/amd64/default/20161107_22:42/ ( only rootfs.tar.xz is needed. Take care to download the template in /var/lib/vz/template/cache, otherwise pct create will fail ( apparmor restriction) Isn’t so important that this image is really minimal, lacking ssh or wget ( that could be installed manually). Fortunately, this images ships with systemd by default. Unfortunately, I couldn’t install yet IspConfig with a standard lxc debian template, inside proxmox, because the installer hangs in different places (I didn’t have this issues with debian-8.0-standard_8.4-1_amd64.tar.gz standard proxmox). It’s worth mentioning that the container is no limited at cpu or memory level. The failing moments aren’t random. First php5-fpm, after memcached, then startup packages. “status half-configured php5-fpm:amd64 5.6.27+dfsg-0+deb8u1” “status half-configured memcached:amd64 1.4.21-1.1+deb8u1” Temporary workaround is to manually install those packages (php5-fpm, memcached) before the general ispconfig installer, but didn’t work for startup packages. Anyway, this is a stoopid solution. The root cause remains unknown for the moment. WORKAROUND 2 - replace sysv with systemd for proxmox lxc debian 8 Following the steps from https://wiki.debian.org/systemd#Configuring_as_default apt-get update + apt-get install systemd apt-get install systemd-sysv reboot ps -p 1 -o comm= ( testing must be systemd) Can't use https://wiki.debian.org/systemd#Debugging, there's not /etc/default/grub inside container. Even at first glance, this looks promising, the problems shows up very soon, so I am stuck also with this branch . After trying apt-get install ntp ntpdate, I get “update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to get D-Bus connection: No such file or directory Failed to get D-Bus connection: No such file or directory Failed to get D-Bus connection: No such file or directory invoke-rc.d: initscript ntp, action "start" failed.” Thanks!