[Bug 1594738] Re: systemctl not working inside chroot

[Martin Pitt]

Sorry, systemd cannot work in a chroot by design. service/invoke-rc.d
can start SysV init scripts, but this is still dangerous and not at all
recommended. chroots should have a policy-rc.d that denies the startup
of services from packages.

If you want to run services in an isolated environment, please use
containers.

** Changed in: systemd (Ubuntu)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1594738

Title:
  systemctl not working inside chroot

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  AFAIU, Ubuntu switched to systemd as its service management system.
  Therefore I expect it to start services even in a chroot environment.

  Using "service apache2 start" instead works without any problems.

  1)
  Description:	Ubuntu 16.04 LTS
  Release:	16.04

  2)
  systemd:
    Installed: 229-4ubuntu4
    Candidate: 229-4ubuntu6
    Version table:
       229-4ubuntu6 500
          500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
   *** 229-4ubuntu4 500
          500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
          100 /var/lib/dpkg/status

  3)
  "systemctl start apache2" should start Apache webserver.

  4)
  "systemctl start apache2" does not start Apache webserver.
  Instead it says

  >Running in chroot, ignoring request.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594738/+subscriptions