I'm exploring Proxmox for the first time (having first considered LXD on Ubuntu 16.04 but failed to find a suitable web management gui).
Timing was perfect with this test release as I'm testing anyway, so I thought I'd try. Manual install on fresh Jessie build.
Initial impressions very positive with 2 VMs and a Jessie lxc container, however I've hit issues trying to create an Ubuntu container...
Neither the 15.10 image from your downloads or a 16.04 image from the Ubuntu published templates will start correctly. Systemd is failing early on, so while I can get a shell in the container, nothing is set up (eg. no network).
I can't be sure having not used a previous Proxmox version, but at least the 15.10 build is tried and tested so it seems to be a systemd issue caused by this release?
Starting 15.10 the messages are:
Starting 16.04 slightly different:
Changing 16.04 over to upstart now works fine, so that's my workaround for now (in fact I've saved a new template based on that for the short term).
Trying to diagnose I see previous mentions in the forum of issues with lxc and older systemd versions, but as noted in the above, both these Ubunutu releases are on newer versions than the jessie host. I also updated a jessie container with systemd-sysv, and that starts OK.
Timing was perfect with this test release as I'm testing anyway, so I thought I'd try. Manual install on fresh Jessie build.
Initial impressions very positive with 2 VMs and a Jessie lxc container, however I've hit issues trying to create an Ubuntu container...
Neither the 15.10 image from your downloads or a 16.04 image from the Ubuntu published templates will start correctly. Systemd is failing early on, so while I can get a shell in the container, nothing is set up (eg. no network).
I can't be sure having not used a previous Proxmox version, but at least the 15.10 build is tried and tested so it seems to be a systemd issue caused by this release?
Starting 15.10 the messages are:
Code:
readline() on closed filehandle $fd at /usr/share/lxc/hooks/lxc-pve-autodev-hook line 32.
systemd 225 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Detected virtualization lxc.
Detected architecture x86-64.
Welcome to Ubuntu 15.10!
Set hostname to <mythtv2>.
Failed to install release agent, ignoring: Input/output error
Failed to create root cgroup hierarchy: No such file or directory
Failed to allocate manager object: No such file or directory
[!!!!!!] Failed to allocate manager object, freezing.Starting 16.04 slightly different:
Code:
readline() on closed filehandle $fd at /usr/share/lxc/hooks/lxc-pve-autodev-hook line 32.
systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
Detected virtualization lxc.
Detected architecture x86-64.
Welcome to Ubuntu 16.04 LTS!
Set hostname to <MythTV>.
Failed to install release agent, ignoring: Input/output error
Failed to create /lxc/102/init.scope control group: No such file or directory
Failed to allocate manager object: No such file or directory
[!!!!!!] Failed to allocate manager object, freezing.
Freezing execution.Trying to diagnose I see previous mentions in the forum of issues with lxc and older systemd versions, but as noted in the above, both these Ubunutu releases are on newer versions than the jessie host. I also updated a jessie container with systemd-sysv, and that starts OK.
