The Linux Containers project includes three subprojects: LXC, LXD and LXCFS. The project also included the CGManager project, which has been deprecated in favor of the CGroup namespace in recent kernels.
Creating and running privileged containers as
root does not require any
configuration; simply use the various
lxc-* commands, such as
Creating unprivileged containers
User IDs (UIDs) and group IDs (GIDs) normally range from 0 to 65535. Unprivileged containers enhance security by mapping UID and GID ranges inside each container to ranges not in use by the host system. The unused host ranges must be subordinated to the user who will be running the unprivileged containers.
Subordinate UIDs and GIDs are assigned in the subuid(5) and subgid(5) files, respectively.
To create unprivileged containers, first edit
delegate ranges. For example:
In each colon-delimited entry:
- the first field is the user to which a subordinate range will be assigned;
- the second field is the smallest numeric ID defining a subordinate range; and
- the third field is the number of consecutive IDs in the range.
The usermod(8) program may also be used to manipulate suborinated IDs.
Generally, the number of consecutive IDs should be an integer multiple of 65536;
the starting value is not important, except to ensure that the various ranges
defined in the file do not overlap. In this example,
root controls UIDs (or,
subgid, GIDs) ranging from 1000000 to 1065535, inclusive;
IDs ranging from 2000000 to 2065535.
Before creating a container, the user owning the container will need an
lxc.conf(5) file specifying the subuid
and subgid range to use. For root-owned containers, this file resides at
/etc/lxc/default.conf; for unprivileged users, the file resides at
~/.config/lxc/default.conf. Mappings are described in lines of the form
lxc.idmap = u 0 1000000 65536 lxc.idmap = g 0 1000000 65536
u character indicates a UID mapping, while the isolated
indicates a GID mapping. The first numeric value should generally always be 0;
this indicates the start of the UID or GID range as seen from within the
container. The second numeric value is the start of the corresponding range as
seen from outside the container, and may be an arbitrary value within the range
/etc/subgid. The final value is the number of
consecutive IDs to map.
Note that, although the external range start is arbitrary, care must be taken to ensure that the end of the range implied by the start and number does not extend beyond the range of IDs delegated to the user.
If configuring a non-root user, edit
/etc/lxc/lxc-usernet as root to specify a
network device quota. For example, to allow the user named
user to create up
veth devices connected to the
user veth lxcbr0 10
The user can now create and use unprivileged containers with the
utilities. To create a simple Void container named
mycontainer, use a command
lxc-create -n mycontainer -t download -- \ --dist voidlinux --release current --arch amd64
You may substitute another architecture for
amd64, and you may specify a
musl image by adding
--variant musl to the end of the command. See the LXC
Image Server for a list of available
By default, configurations and mountpoints for system containers are stored in
/var/lib/lxc, while configurations for user containers and mountpoints are
~/.local/share/lxc. Both of these values can be modified by setting
lxc.lxcpath in the
lxc.system.conf(5) file. The
superuser may launch unprivileged containers in the system
/etc/lxc/lxc.conf; regular users may launch unprivileged containers in the
lxc.lxcpath defined in
All containers will share the same subordinate UID and GID maps by default. This
is permissible, but it means that an attacker who gains elevated access within
one container, and can somehow break out of that container, will have similar
access to other containers. To isolate containers from each other, alter the
lxc.idmap ranges in
default.conf to point to a unique range before you
create each container. Trying to fix permissions on a container created with the
wrong map is possible, but inconvenient.
LXD provides an alternative interface to LXC's
lxc-* utilities. However, it
does not require the configuration described in the previous section.
lxd package, and enable
LXD users must belong to the
lxc command to manage instances, as described