procps postinst fails when inside lxd

[Robie Basak]

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)]

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)]

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

[Serge Hallyn (serge-hallyn)]

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