Comment 34 for bug 1727355

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

# grep -a container /proc/1/environ
container=lxc

Because of the juju deb post-inst script running 'invoke-rc.d procps restart' you will get an error message from systemd on the console when installing this package in a LXD container.

Is the 'invoke-rc.d procps restart' necessary and could it benefit from special handling when run in a LXD container?

Output:
Setting up juju-2.0 (2.2.6-0ubuntu0.16.04.3) ...
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 "restart" failed.
● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2017-11-24 09:31:03 UTC; 6ms ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 751 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
 Main PID: 751 (code=exited, status=1/FAILURE)

Nov 24 09:31:03 mgr systemd[1]: Starting Apply Kernel Variables...
Nov 24 09:31:03 mgr systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
Nov 24 09:31:03 mgr systemd[1]: Failed to start Apply Kernel Variables.
Nov 24 09:31:03 mgr systemd[1]: systemd-sysctl.service: Unit entered failed state.
Nov 24 09:31:03 mgr systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.