Update disabling of services in the LXC to the systemd way
Bug #1435480 reported by
Christopher Townsend
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:/
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 |
To post a comment you must log in.
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.