Update getting-started.md #719
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -399,10 +399,15 @@ Next up is `/etc/lxc/lxc-usernet` which is used to set network devices quota for | |
|
|
||
| This means that "your-username" is allowed to create up to 10 veth devices connected to the lxcbr0 bridge. | ||
|
|
||
| Create the `~/.local/share/lxc` directory if it doesn't exist and ensure `~/.local` is executable. | ||
|
|
||
| mkdir -p ~/.local/share/lxc && chmod -R +x ~/.local | ||
|
|
||
| With that done, the last step is to create an LXC configuration file. | ||
|
|
||
| * Create the `~/.config/lxc` directory if it doesn't exist. | ||
| * Copy `/etc/lxc/default.conf` to `~/.config/lxc/default.conf` | ||
| * Set `lxc.apparmor.profile = lxc-container-default-cgns` | ||
| * Append the following two lines to it: | ||
| * `lxc.idmap = u 0 100000 65536` | ||
| * `lxc.idmap = g 0 100000 65536` | ||
|
|
@@ -430,7 +435,11 @@ The download template will show you a list of distributions, versions, and archi | |
|
|
||
| To run unprivileged containers as an unprivileged user, the user must be allocated an empty delegated cgroup (this is required because of the leaf-node and delegation model of cgroup2, not because of liblxc). See [cgroups: Full cgroup2 support](/lxc/news/2020_03_25_13_03.html#cgroups-full-cgroup2-support) for more information. | ||
|
|
||
| In newer versions of lxc, to start a container, use the following command instead of just `lxc-start mycontainer`: | ||
|
|
||
| lxc-unpriv-start --name mycontainer | ||
|
There was a problem hiding this comment. This is a distro-specific command, not an upstream one |
||
|
|
||
| In older versions of lxc it's not possible to simply start a container from a shell as a user and automatically delegate a cgroup. Therefore, you need to wrap each call to any of the `lxc-*` commands in a `systemd-run` command. For example, to start a container, use the following command instead of just `lxc-start mycontainer`: | ||
|
|
||
| systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start --name mycontainer | ||
|
|
||
|
|
@@ -443,7 +452,7 @@ You can then confirm its status with either of: | |
|
|
||
| And get a shell inside it with: | ||
|
|
||
| lxc-unpriv-attach --name mycontainer | ||
|
There was a problem hiding this comment. This is a distro-specific command, not an upstream one There was a problem hiding this comment. For distros without There was a problem hiding this comment. @stgraber would you care to answer so that I may fix this document properly? |
||
|
|
||
| Stopping it can be done with: | ||
|
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This allows things we should not allow by default, yes modern systemd needs it in some cases but that's still not a good idea to have it recommended by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's clear that copying the default config as recommended has
generateset which fails for unprivileged containers started by a user. Considering this part of the guide is for that use case, what would be recommend default if the current recommendation fails?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lxc-container-defaultis the safe profileThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay. I guess that is confusing given the manpages saying
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is
lxc-container-defaultonly recommended for non cgroup systems? Is there ever a time whenlxc-container-defaultis appropriate for cgroup v2 systems? Can you be a little more explicit about these safety problems you are referring to?