Ubuntu
systemd package

  1. Bug #1305395
  2. Comment #2

Comment 2 for bug 1305395

Revision history for this message
Martin Pitt (pitti) wrote :

Indeed the --no-start bit is entirely obsolete now. It was only needed for intra-saucy upgrades while it was still in development, so I think it's best to drop it entirely.

On a "real" system that works fine, I tested clean install and upgrades. However, with that it now fails in LXC as mounting /sys/fs/cgroup/systemd/ does not work in LXC (it only mounts read-only, and mount exits with code 32), which is causing the package to fail to install.

I think that's what Stéphane's cgroupmanager patch is supposed to handle, isn't it? So we should change the upstart job to do something like that:

- if ! mountpoint -q /sys/fs/cgroup/systemd; then
+ if [ ! -e /run/container_type ] && ! mountpoint -q /sys/fs/cgroup/systemd; then
           # ... mount /sys/fs/cgroup/systemd

to avoid the failure. With that, the package installs cleanly in LXC, too. Stéphane, does that look correct?