procps postinst fails when inside lxd

Bug #1580984 reported by Robie Basak on 2016-05-12
This bug affects 3 people
Affects Status Importance Assigned to Milestone
lxd (Ubuntu)
systemd (Ubuntu)

Bug Description

lxc launch ubuntu:xenial test
lxc exec test bash
systemctl status systemd-sysctl.service # note that this is failed
dpkg-reconfigure procps # this attempts to start the service and fails with exit status 1

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Job for systemd-sysctl.service failed because the control process exited with error code. See "systemctl status systemd-sysctl.service" and "journalctl -xe" for details.
invoke-rc.d: initscript procps, action "start" failed.

This causes a dist-upgrade from wily inside a container to fail. Workaround: "systemctl mask systemd-sysctl.service" before doing anything.

I see that /lib/systemd/system/systemd-sysctl.service already defines "ConditionPathIsReadWrite=/proc/sys/". If this is expected to work, presumably it isn't?

Robie Basak (racb) wrote :

Using Xenial with lxd 2.0.0-0ubuntu4 on the host, and that's what I get in the guest on Xenial.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lxd (Ubuntu):
status: New → Confirmed
Serge Hallyn (serge-hallyn) wrote :

procps has a patch to sysctl.c to ignore EACCESS. I guess systemd's systemd-sysctl needs the same kind of patch.

Changed in lxd (Ubuntu):
status: Confirmed → Invalid
Changed in systemd (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers