Ubuntu 14.04 LXC needs to be started manually with init 3 on Proxmox 7

[dsh]

I have some legacy code running on Ubuntu 14.04 LXC.
Since upgrading to Proxmox 7, my 14.04 container starts but doesn't even start up network interfaces and other apps.

If I manually enter to the container with 'pct enter' command and enter 'init 3', everything works.

It worked fine with Proxmox 6. Confirmed with two different host and different 14.04 containers.

 

[oguz]

hi,

ubuntu 14.04 has a systemd version which is too old to run inside the new cgroupv2 environments [0] (default in PVE 7.x, PVE 6.x used cgroupv1)

in the linked page you can find some recommendations or workarounds.

[0]: https://pve.proxmox.com/pve-docs/chapter-pct.html#pct_cgroup_compat

 

[filipealvarez]

> If I manually enter to the container with 'pct enter' command and enter 'init 3', everything works.

Its stable?

Someone know if this is dangerous to host (PVE 7.x) ?

 

[dsh]

> If I manually enter to the container with 'pct enter' command and enter 'init 3', everything works.

Its stable?

Someone know if this is dangerous to host (PVE 7.x) ?

It's been stable for at least 2 months right now.

 

[Ihor]

I have some legacy code running on Ubuntu 14.04 LXC.
Since upgrading to Proxmox 7, my 14.04 container starts but doesn't even start up network interfaces and other apps.

If I manually enter to the container with 'pct enter' command and enter 'init 3', everything works.

It worked fine with Proxmox 6. Confirmed with two different host and different 14.04 containers.

Unfortunately I've faced with legacy project too on Ubuntu 14. And as for the services initialization I've developed following solution:

/etc/init/workaround-init-for_old_cgroup.conf

# Containers with the old cgroup such as ubuntu 14 doesn't initialize services at startup
# So we have to run them "manually"

description    "Workaround for initialization a container with the old cgroup"

emits socket

start on net-device-up IFACE=lo

exec /root/bin/workaround-init-for_old_cgroup.sh

/root/bin/workaround-init-for_old_cgroup.sh

#!/usr/bin/env bash

# Containers with the old cgroup such as ubuntu 14 doesn't initialize services at startup
# So we have to run them "manually"

# Run services if they are stopped
if [ $(/sbin/initctl list | grep networking | grep -c stop) -ge 1 ]; then
  echo "Run services with $0"
  # First of all run syslog
  /etc/init.d/rsyslog start
  # init all
  /sbin/init 3
  # Other services which haven't been executed by init command
  /etc/init.d/udev start
else
  echo "Services are already running with $0"
fi

I hope this will probably be helpful.

 

[idariel]

Unfortunately I've faced with legacy project too on Ubuntu 14. And as for the services initialization I've developed following solution:

/etc/init/workaround-init-for_old_cgroup.conf

# Containers with the old cgroup such as ubuntu 14 doesn't initialize services at startup
# So we have to run them "manually"

description    "Workaround for initialization a container with the old cgroup"

emits socket

start on net-device-up IFACE=lo

exec /root/bin/workaround-init-for_old_cgroup.sh

/root/bin/workaround-init-for_old_cgroup.sh

#!/usr/bin/env bash

# Containers with the old cgroup such as ubuntu 14 doesn't initialize services at startup
# So we have to run them "manually"

# Run services if they are stopped
if [ $(/sbin/initctl list | grep networking | grep -c stop) -ge 1 ]; then
  echo "Run services with $0"
  # First of all run syslog
  /etc/init.d/rsyslog start
  # init all
  /sbin/init 3
  # Other services which haven't been executed by init command
  /etc/init.d/udev start
else
  echo "Services are already running with $0"
fi

I hope this will probably be helpful.

Excellent post, very useful. Thank you very much.