Project configuration#
Projects can be configured through a set of key/value configuration options. See Configure a project for instructions on how to set these options.
The key/value configuration is namespaced. The following options are available:
Project features#
The project features define which entities are isolated in the project and which are inherited from the default
project.
If a feature.*
option is set to true
, the corresponding entity is isolated in the project.
Note
When you create a project without explicitly configuring a specific option, this option is set to the initial value given in the following table.
However, if you unset one of the feature.*
options, it does not go back to the initial value, but to the default value.
The default value for all feature.*
options is false
.
Key |
Type |
Default |
Initial value |
Description |
---|---|---|---|---|
|
bool |
|
|
Whether to use a separate set of images and image aliases for the project |
|
bool |
|
|
Whether to use a separate set of networks for the project |
|
bool |
|
|
Whether to use a separate set of network zones for the project |
|
bool |
|
|
Whether to use a separate set of profiles for the project |
|
bool |
|
|
Whether to use a separate set of storage buckets for the project |
|
bool |
|
|
Whether to use a separate set of storage volumes for the project |
Project limits#
Project limits define a hard upper bound for the resources that can be used by the containers and VMs that belong to a project.
Depending on the limits.*
option, the limit applies to the number of entities that are allowed in the project (for example, limits.containers
or limits.networks
) or to the aggregate value of resource usage for all instances in the project (for example, limits.cpu
or limits.processes
).
In the latter case, the limit usually applies to the Resource limits that are configured for each instance (either directly or via a profile), and not to the resources that are actually in use.
For example, if you set the project’s limits.memory
configuration to 50GB
, the sum of the individual values of all limits.memory
configuration keys defined on the project’s instances will be kept under 50 GB.
If you try to create an instance that would make the total sum of limits.memory
configurations exceed 50 GB, you will get an error.
Similarly, setting the project’s limits.cpu
configuration key to 100
means that the sum of individual limits.cpu
values will be kept below 100.
When using project limits, the following conditions must be fulfilled:
When you set one of the
limits.*
configurations and there is a corresponding configuration for the instance, all instances in the project must have the corresponding configuration defined (either directly or via a profile). See Resource limits for the instance configuration options.The
limits.cpu
configuration cannot be used if CPU pinning is enabled. This means that to uselimits.cpu
on a project, thelimits.cpu
configuration of each instance in the project must be set to a number of CPUs, not a set or a range of CPUs.The
limits.memory
configuration must be set to an absolute value, not a percentage.
Key |
Type |
Default |
Description |
---|---|---|---|
|
integer |
- |
Maximum number of containers that can be created in the project |
|
integer |
- |
Maximum value for the sum of individual |
|
string |
- |
Maximum value of aggregate disk space used by all instance volumes, custom volumes, and images of the project |
|
integer |
- |
Maximum number of total instances that can be created in the project |
|
string |
- |
Maximum value for the sum of individual |
|
integer |
- |
Maximum number of networks that the project can have |
|
integer |
- |
Maximum value for the sum of individual |
|
integer |
- |
Maximum number of VMs that can be created in the project |
Project restrictions#
To prevent the instances of a project from accessing security-sensitive features (such as container nesting or raw LXC configuration), set the restricted
configuration option to true
.
You can then use the various restricted.*
options to pick individual features that would normally be blocked by restricted
and allow them, so they can be used by the instances of the project.
For example, to restrict a project and block all security-sensitive features, but allow container nesting, enter the following commands:
lxc project set <project_name> restricted=true
lxc project set <project_name> restricted.containers.nesting=allow
Each security-sensitive feature has an associated restricted.*
project configuration option.
If you want to allow the usage of a feature, change the value of its restricted.*
option.
Most restricted.*
configurations are binary switches that can be set to either block
(the default) or allow
.
However, some options support other values for more fine-grained control.
Note
You must set the restricted
configuration to true
for any of the restricted.*
options to be effective.
If restricted
is set to false
, changing a restricted.*
option has no effect.
Setting all restricted.*
keys to allow
is equivalent to setting restricted
itself to false
.
Key |
Type |
Default |
Description |
---|---|---|---|
|
bool |
|
Whether to block access to security-sensitive features - must be enabled to allow the |
|
string |
|
Prevents creating any instance or volume backups |
|
string |
- |
Prevents targeting cluster groups other than the provided ones |
|
string |
|
Prevents direct targeting of cluster members when creating or moving instances |
|
string |
|
Prevents using low-level container options like |
|
string |
|
Prevents setting |
|
string |
|
Prevents configuring privileged containers ( |
|
string |
|
Prevents using system call interception options - when set to |
|
string |
|
Prevents using disk devices ( |
|
string |
- |
If |
|
string |
|
Prevents using devices of type |
|
string |
|
Prevents using devices of type |
|
string |
|
Prevents using network devices and controls access to networks ( |
|
string |
|
Prevents using devices of type |
|
string |
|
Prevents using devices of type |
|
string |
|
Prevents using devices of type |
|
string |
|
Prevents using devices of type |
|
string |
|
Prevents using devices of type |
|
string |
|
Prevents using devices of type |
|
string |
- |
Specifies the host UID ranges allowed in the instance’s |
|
string |
- |
Specifies the host GID ranges allowed in the instance’s |
|
string |
- |
Comma-delimited list of network names that are allowed for use in this project - if not set, all networks are accessible (this setting depends on the |
|
string |
|
Comma-delimited list of network subnets from the uplink networks (in the form |
|
string |
|
Comma-delimited list of network names that can be used as uplink for networks in this project |
|
string |
|
Comma-delimited list of network zones that can be used (or something under them) in this project |
|
string |
|
Prevents creating any instance or volume snapshots |
|
string |
|
Prevents using low-level VM options like |
Project-specific configuration#
There are some Server configuration options that you can override for a project. In addition, you can add user metadata for a project.
Key |
Type |
Default |
Description |
---|---|---|---|
|
string |
- |
Compression algorithm to use for backups ( |
|
bool |
- |
Whether to automatically update any image that LXD caches |
|
integer |
- |
Interval (in hours) at which to look for updates to cached images ( |
|
string |
- |
Compression algorithm to use for new images ( |
|
string |
- |
Default architecture to use in a mixed-architecture cluster |
|
integer |
- |
Number of days after which an unused cached remote image is flushed in the project |
|
string |
- |
User-provided free-form key/value pairs |