Update disabling of services in the LXC to the systemd way

Bug #1435480 reported by Christopher Townsend
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity8 Desktop Preview in LXC
Triaged
High
Christopher Townsend
unity8-lxc (Ubuntu)
Triaged
High
Christopher Townsend

Bug Description

The unity8-lxc-setup disables services in the container. With the old upstart way, it would create an override file, but this does not apply for systemd.

According to https://wiki.ubuntu.com/SystemdForUpstartUsers, the Upstart manual method is now replaced with calling 'systemctl disable foo.service' where foo is the name of the service not to run at session init.

Changed in unity8-preview-lxc:
status: New → In Progress
Changed in unity8-lxc (Ubuntu):
status: New → In Progress
Changed in unity8-preview-lxc:
importance: Undecided → High
Changed in unity8-lxc (Ubuntu):
importance: Undecided → High
Changed in unity8-preview-lxc:
assignee: nobody → Christopher Townsend (townsend)
Changed in unity8-lxc (Ubuntu):
assignee: nobody → Christopher Townsend (townsend)
Changed in unity8-preview-lxc:
milestone: none → 1.0.4
Revision history for this message
Christopher Townsend (townsend) wrote :

systemd based containers are currently broken, so until this is fixed, I'm not going to work on this. The workaround is to install upstart-sysv in the container and not use systemd.

When systemd is working for the containers, then I'll revisit this issue.

Changed in unity8-preview-lxc:
status: In Progress → Triaged
Changed in unity8-lxc (Ubuntu):
status: In Progress → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.