Unprivileged LXC container does not start with step by step usage instructions
Bug #1612533 reported by
Andreas
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Server Guide |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Following the steps in https:/
Depending on your initial installed packages, it might be required to open a new shell, otherwise the "lxc-start -n u1 -d" step might fail.
Some text as per Serge's comment #6 below should be added to clarify this possible requirement.
description: | updated |
Changed in serverguide: | |
status: | New → Confirmed |
To post a comment you must log in.
I tested that exact area of the documentation on a brand new 16.04 server VM during the 16.04 cycle, and it worked fine. As far as I have been able to determine the package cgmanager is installed by default on a new sever, so we need to figure out what is different between our two installs.