LXC/LXD containers should be automatically started on user login and then subsequently frozen
Bug #1654356 reported by
Christopher Townsend
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Libertine | Status tracked in Devel | |||||
| Devel |
Triaged
|
Medium
|
Unassigned | |||
| Trunk |
Triaged
|
Medium
|
Unassigned | |||
| libertine (Ubuntu) |
Triaged
|
Medium
|
Unassigned | |||
Bug Description
To go along with bug #1654355, LXC/LXD containers should be set to automatically start on user session login, and then they should be subsequently frozen until needed.
We should think about if this should be configurable if anyone does not want the container to start on login.
Note: I originally had this as starting a container on host boot, that will cause problems since the containers are unprivileged and need user info when starting.
| description: | updated |
| summary: |
LXC/LXD containers should be automatically started on host boot and then - subsuquently frozen + subsequently frozen |
| Changed in libertine (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: lxc lxd |
| summary: |
- LXC/LXD containers should be automatically started on host boot and then - subsequently frozen + LXC/LXD containers should be automatically started on user login and + then subsequently frozen |
| description: | updated |
| Changed in libertine: | |
| milestone: | 1.6 → 1.7 |
To post a comment you must log in.
