LinuxContainers

https://linuxcontainers.org/
Admin
An umbrella project providing distro and vendor neutral environment for Linux container and virtual...
Tokens:1,635,221
Snippets:15,226
Trust Score:9.9
Update:6 days ago
Show doc for...
Tokens:
Raw
### incus create examples

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/create.md.txt

Three examples showing how to create an instance, create with configuration from a file, and create and start a virtual machine with disk overrides.

```bash
  incus create images:debian/12 u1
      Create the instance u1

  incus create images:debian/12 u1 < config.yaml
      Create the instance with configuration from config.yaml

  incus launch images:debian/12 v2 --vm -d root,size=50GiB -d root,io.bus=nvme
      Create and start a virtual machine, overriding the disk size and bus
```

--------------------------------

### incus launch examples

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/launch.md.txt

Examples of using `incus launch` to create and start containers and virtual machines with various options.

```bash
  incus launch images:debian/12 c1
      Create and start a container named "c1"

  incus launch images:debian/12 c2 < config.yaml
      Create and start a container named "c2" with configuration from config.yaml

  incus launch images:debian/12 c3 -t aws:t2.micro
      Create and start a container named "c3" using the same size as an AWS t2.micro (1 vCPU, 1GiB of RAM)
      Find the list of supported instance types here: https://images.linuxcontainers.org/meta/instance-types/

  incus launch images:debian/12 v1 --vm -c limits.cpu=4 -c limits.memory=4GiB
      Create and start a virtual machine named "v1" with 4 vCPUs and 4GiB of RAM

  incus launch images:debian/12 v2 --vm -d root,size=50GiB -d root,io.bus=nvme
      Create and start a virtual machine named "v2", overriding the disk size and bus
```

--------------------------------

### incus launch examples

Source: https://linuxcontainers.org/incus/docs/main/reference/manpages/incus/launch

Examples of creating and starting containers and virtual machines with various options, including configuration from file, instance type, resource limits, and disk overrides.

```bash
  incus launch images:debian/12 c1
      Create and start a container named "c1"

  incus launch images:debian/12 c2 < config.yaml
      Create and start a container named "c2" with configuration from config.yaml

  incus launch images:debian/12 c3 -t aws:t2.micro
      Create and start a container named "c3" using the same size as an AWS t2.micro (1 vCPU, 1GiB of RAM)
      Find the list of supported instance types here: https://images.linuxcontainers.org/meta/instance-types/

  incus launch images:debian/12 v1 --vm -c limits.cpu=4 -c limits.memory=4GiB
      Create and start a virtual machine named "v1" with 4 vCPUs and 4GiB of RAM

  incus launch images:debian/12 v2 --vm -d root,size=50GiB -d root,io.bus=nvme
      Create and start a virtual machine named "v2", overriding the disk size and bus

```

--------------------------------

### lxc.hook.start-host example: network setup script

Source: https://linuxcontainers.org/fr/lxc/news/2018_03_27_21_15.html

Example configuration and script for using lxc.hook.start-host to set up networking in a root-owned container, including placing a veth peer into the container's network namespace using LXC_PID.

```ini
lxc.net.0.type = empty
lxc.hook.start-host = /bin/lxc-start-netns
```

```bash
echo "starting" > /tmp/debug
ip link add host1 type veth peer name peer1
ip link set host1 master lxcbr0
ip link set host1 up
ip link set peer1 netns "${LXC_PID}"
```

--------------------------------

### lxc.hook.start-host example: network setup script

Source: https://linuxcontainers.org/de/lxc/news/2018_03_27_21_15.html

Example configuration and script for using lxc.hook.start-host to set up networking in a root-owned container, including a script that creates a veth pair and moves one end into the container's network namespace.

```ini
lxc.net.0.type = empty
lxc.hook.start-host = /bin/lxc-start-netns
```

```bash
echo "starting" > /tmp/debug
ip link add host1 type veth peer name peer1
ip link set host1 master lxcbr0
ip link set host1 up
ip link set peer1 netns "${LXC_PID}"
```

--------------------------------

### Start IncusOS virtual machine

Source: https://linuxcontainers.org/incus-os/docs/main/getting-started/installation/virtual-incus

Starts the IncusOS virtual machine to begin the installation process.

```bash
incus start IncusOS

```

--------------------------------

### Examples of retrieving volume configuration

Source: https://linuxcontainers.org/incus/docs/main/reference/manpages/incus/storage/volume/get

Two examples demonstrating how to get the size of a custom volume and the snapshot expiration period for a virtual machine.

```bash
  incus storage volume get default data size
      Returns the size of a custom volume "data" in pool "default"

  incus storage volume get default virtual-machine/data snapshots.expiry
      Returns the snapshot expiration period for a virtual machine "data" in pool "default"
```

--------------------------------

### incus file mount examples

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/file/mount.md.txt

Two examples: mounting /root from instance foo to local directory fooroot, and starting an SSH SFTP listener for the root filesystem of instance foo.

```bash
  incus file mount foo/root fooroot
     To mount /root from the instance foo onto the local fooroot directory.

  incus file mount foo
     To start an SSH SFTP listener for the root filesystem of instance foo.
```

--------------------------------

### incus file mount examples

Source: https://linuxcontainers.org/incus/docs/main/reference/manpages/incus/file/mount

Two usage examples: mounting /root from instance foo to local directory fooroot, and starting an SSH SFTP listener for the root filesystem of instance foo.

```bash
  incus file mount foo/root fooroot
     To mount /root from the instance foo onto the local fooroot directory.

  incus file mount foo
     To start an SSH SFTP listener for the root filesystem of instance foo.

```

--------------------------------

### Services seed YAML example

Source: https://linuxcontainers.org/incus-os/docs/main/_sources/reference/seed.md.txt

Example YAML configuration for the services seed file, showing how to enable the tailscale and lvm services. The seed is applied on first boot before services start. Note that services requiring an application that isn't installed yet (ceph and linstor) cannot be configured through the services seed.

```yaml
version: "1"
tailscale:
  enabled: true
  auth_key: tskey-auth-XXXXXXXXXXXX
lvm:
  enabled: true

```

--------------------------------

### GET /1.0/applications

Source: https://linuxcontainers.org/incus-os/docs/main/reference/api

Get currently installed applications.

```APIDOC
## GET /1.0/applications

### Description
Get currently installed applications.

### Method
GET

### Endpoint
/1.0/applications
```

--------------------------------

### Configure cloud-init user-data in Incus instance config

Source: https://linuxcontainers.org/incus/docs/main/_sources/cloud-init.md.txt

Use YAML literal style with a pipe symbol to pass cloud-init user-data as a single string. The example sets package_upgrade and installs two packages. Configure before first start.

```yaml
config:
  cloud-init.user-data: |
    #cloud-config
    package_upgrade: true
    packages:
      - package1
      - package2
```

--------------------------------

### GET query examples for filtering

Source: https://linuxcontainers.org/incus/docs/main/rest-api

Three examples of GET queries using different filtering methods: logical operators, nested fields, and negation.

```text
containers?filter=name eq "my container" and status eq Running

```

```text
containers?filter=config.image.os eq ubuntu or devices.eth0.nictype eq bridged

```

```text
images?filter=Properties.os eq Centos and not UpdateSource.Protocol eq simplestreams

```

--------------------------------

### incus storage volume get examples

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/storage/volume/get.md.txt

Two examples showing how to get the size of a custom volume and the snapshot expiration period for a virtual machine.

```bash
incus storage volume get default data size
    Returns the size of a custom volume "data" in pool "default"

incus storage volume get default virtual-machine/data snapshots.expiry
    Returns the snapshot expiration period for a virtual machine "data" in pool "default"
```

--------------------------------

### incus create examples

Source: https://linuxcontainers.org/incus/docs/main/reference/manpages/incus/create

Examples of creating instances: basic creation, creation with configuration from a file, and creation of a virtual machine with device overrides.

```bash
  incus create images:debian/12 u1
      Create the instance u1

  incus create images:debian/12 u1 < config.yaml
      Create the instance with configuration from config.yaml

  incus launch images:debian/12 v2 --vm -d root,size=50GiB -d root,io.bus=nvme
      Create and start a virtual machine, overriding the disk size and bus

```

--------------------------------

### Examples: create template for instance

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/config/template/create.md.txt

Two examples: create template t1 for instance u1, and create it from a file config.tpl.

```bash
  incus config template create u1 t1
      Create template t1 for instance u1

  incus config template create u1 t1 < config.tpl
      Create template t1 for instance u1 from config.tpl
```

--------------------------------

### incus start v1 --override-boot with interactive boot entry selection

Source: https://linuxcontainers.org/de/incus/news/index.html

Run `incus start v1 --override-boot` to interactively select the next boot entry for a virtual machine. The command displays a table of boot entries from the NVRAM and prompts for a selection. In this example, the user selects entry 1 (EFI Firmware Setup).

```shell
stgraber@vorash:~$ incus start v1 --override-boot
┌────┬────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ ID │          DESCRIPTION           │                                          PATH                                          │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 0  │ BootManagerMenuApp             │ Fv(64074afe-340a-4be6-94ba-91b5b4d0f71e)/FvFile(eec25bdc-67f2-4d95-b1d5-f81b2039d11d)  │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 1  │ EFI Firmware Setup             │ Fv(64074afe-340a-4be6-94ba-91b5b4d0f71e)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)  │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 2  │ UEFI QEMU QEMU HARDDISK        │ PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/Scsi(0x0,0x1)                                   │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 3  │ UEFI PXEv4 (MAC:10666AA0CED7)  │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv4(0.0.0.0,0x0)         │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 4  │ UEFI PXEv6 (MAC:10666AA0CED7)  │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv6(::,0x0,Static)       │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 5  │ UEFI HTTPv4 (MAC:10666AA0CED7) │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv4(0.0.0.0,0x0)/Uri()   │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 6  │ UEFI HTTPv6 (MAC:10666AA0CED7) │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv6(::,0x0,Static)/Uri() │
└────┴────────────────────────────────┴────────────────────────────────────────────────────────────────────────────────────────┘
Select next boot entry: 1

```

--------------------------------

### Start dns, web, NULL, and onboot groups in order

Source: https://linuxcontainers.org/fr/lxc/manpages//man1/lxc-autostart.1.html

Example of using -g to start the 'dns' group, then 'web', then the NULL group, and finally 'onboot'. Equivalent to -g dns,web -g ,onboot or -g dns -g web -g "" -g onboot.

```bash
-g "dns,web,,onboot"
```

--------------------------------

### GET query examples for filtering

Source: https://linuxcontainers.org/incus/docs/main/_sources/rest-api.md.txt

Three examples of GET queries using different filtering methods, including logical operators and quoting values with spaces.

```text
containers?filter=name eq "my container" and status eq Running
```

```text
containers?filter=config.image.os eq ubuntu or devices.eth0.nictype eq bridged
```

```text
images?filter=Properties.os eq Centos and not UpdateSource.Protocol eq simplestreams
```

--------------------------------

### incus start --override-boot interactive boot entry selection

Source: https://linuxcontainers.org/de/incus/news

Run incus start v1 --override-boot to interactively select a boot entry from the VM's NVRAM. The command displays a numbered table of boot entries and prompts 'Select next boot entry:'. In this example, entry 1 (EFI Firmware Setup) is selected.

```bash
stgraber@vorash:~$ incus start v1 --override-boot
┌────┬────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ ID │          DESCRIPTION           │                                          PATH                                          │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 0  │ BootManagerMenuApp             │ Fv(64074afe-340a-4be6-94ba-91b5b4d0f71e)/FvFile(eec25bdc-67f2-4d95-b1d5-f81b2039d11d)  │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 1  │ EFI Firmware Setup             │ Fv(64074afe-340a-4be6-94ba-91b5b4d0f71e)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)  │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 2  │ UEFI QEMU QEMU HARDDISK        │ PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/Scsi(0x0,0x1)                                   │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 3  │ UEFI PXEv4 (MAC:10666AA0CED7)  │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv4(0.0.0.0,0x0)         │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 4  │ UEFI PXEv6 (MAC:10666AA0CED7)  │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv6(::,0x0,Static)       │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 5  │ UEFI HTTPv4 (MAC:10666AA0CED7) │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv4(0.0.0.0,0x0)/Uri()   │
├────┼────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ 6  │ UEFI HTTPv6 (MAC:10666AA0CED7) │ PciRoot(0x0)/Pci(0x1,0x4)/Pci(0x0,0x0)/MAC(10666aa0ced7,0x1)/IPv6(::,0x0,Static)/Uri() │
└────┴────────────────────────────────┴────────────────────────────────────────────────────────────────────────────────────────┘
Select next boot entry: 1
```

--------------------------------

### Set instance start protection and attempt to start

Source: https://linuxcontainers.org/id/incus/news/index.html

Shows how to set the `security.protection.start` configuration key to `true` on an instance and then attempt to start it, which results in an error because the instance is protected.

```bash
stgraber@vorash:~$ incus config set c1 security.protection.start=true
stgraber@vorash:~$ incus start c1
Error: Instance is protected against being started

```

--------------------------------

### incus file create examples

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/file/create.md.txt

Two examples: creating a file /bar in instance foo, and creating a symlink /bar in instance foo with target baz.

```bash
  incus file create foo/bar
     To create a file /bar in the foo instance.

  incus file create --type=symlink foo/bar baz
     To create a symlink /bar in instance foo whose target is baz.
```

--------------------------------

### C API example: create, start, stop, and destroy a container

Source: https://linuxcontainers.org/fr/lxc/documentation

A simple C program using the LXC API to create, start, stop, and destroy a container. It includes error handling and cleanup. The example uses lxc_container_new, createl, start, shutdown, stop, destroy, and lxc_container_put.

```c
#include <stdio.h>

#include <lxc/lxccontainer.h>

int main() {
    struct lxc_container *c;
    int ret = 1;

    /* Setup container struct */
    c = lxc_container_new("apicontainer", NULL);
    if (!c) {
        fprintf(stderr, "Failed to setup lxc_container struct\n");
        goto out;
    }

    if (c->is_defined(c)) {
        fprintf(stderr, "Container already exists\n");
        goto out;
    }

    /* Create the container */
    if (!c->createl(c, "download", NULL, NULL, LXC_CREATE_QUIET,
                    "-d", "ubuntu", "-r", "trusty", "-a", "i386", NULL)) {
        fprintf(stderr, "Failed to create container rootfs\n");
        goto out;
    }

    /* Start the container */
    if (!c->start(c, 0, NULL)) {
        fprintf(stderr, "Failed to start the container\n");
        goto out;
    }

    /* Query some information */
    printf("Container state: %s\n", c->state(c));
    printf("Container PID: %d\n", c->init_pid(c));

    /* Stop the container */
    if (!c->shutdown(c, 30)) {
        printf("Failed to cleanly shutdown the container, forcing.\n");
        if (!c->stop(c)) {
            fprintf(stderr, "Failed to kill the container.\n");
            goto out;
        }
    }

    /* Destroy the container */
    if (!c->destroy(c)) {
        fprintf(stderr, "Failed to destroy the container.\n");
        goto out;
    }

    ret = 0;
out:
    lxc_container_put(c);
    return ret;
}

```

--------------------------------

### Start migrated instances and verify running

Source: https://linuxcontainers.org/incus-os/docs/main/tutorials/storage-import-unencrypted-incus-pool

Starts all instances on the server and then lists them to verify they are running with the encrypted storage volume.

```bash
$ for instance in $(incus list --columns n --format compact,noheader); do incus start $instance; done
$ incus list
┌─────────────┬─────────┬───────────────────────┬──────────────────────────────────────────────────┬─────────────────┬───────────┐
│    NAME     │  STATE  │         IPV4          │                       IPV6                       │      TYPE       │ SNAPSHOTS │
├─────────────┼─────────┼───────────────────────┼──────────────────────────────────────────────────┼─────────────────┼───────────┤
│ debian13    │ RUNNING │ 10.203.93.68 (eth0)   │ fd42:39f9:1631:1319:1266:6aff:fe7f:88f7 (eth0)   │ CONTAINER       │ 0         │
├─────────────┼─────────┼───────────────────────┼──────────────────────────────────────────────────┼─────────────────┼───────────┤
│ debian13-vm │ RUNNING │ 10.203.93.75 (enp5s0) │ fd42:39f9:1631:1319:1266:6aff:fec3:b763 (enp5s0) │ VIRTUAL-MACHINE │ 0         │
└─────────────┴─────────┴───────────────────────┴──────────────────────────────────────────────────┴─────────────────┴───────────┘
```

--------------------------------

### get_nvram_var(guid, name)

Source: https://linuxcontainers.org/incus/docs/main/reference/instance_options

Gets an NVRAM variable.

```APIDOC
## get_nvram_var(guid, name)

### Description
Gets an NVRAM variable.

### Parameters
- **guid** (string) - Required - The GUID of the variable.
- **name** (string) - Required - The name of the variable.

### Returns
- The value of the NVRAM variable.

### Notes
- Only available with EDK2 firmware.
```

--------------------------------

### incus project create examples

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/project/create.md.txt

Two examples: creating a project named p1, and creating a project named p1 with configuration from config.yaml.

```bash
  incus project create p1
      Create a project named p1

  incus project create p1 < config.yaml
      Create a project named p1 with configuration from config.yaml
```

--------------------------------

### Install distrobuilder with go install

Source: https://linuxcontainers.org/de/distrobuilder/introduction

Installs the current build of distrobuilder directly from the latest version on GitHub. Use this command to get the latest development version without downloading a release tarball.

```bash
go install -v -x github.com/lxc/distrobuilder/distrobuilder@latest

```

--------------------------------

### Create minimal setup with incus admin init --minimal

Source: https://linuxcontainers.org/incus/docs/main/howto/initialize

Use the --minimal flag to skip the interactive configuration steps and create a basic setup with default options. Note that this configuration is not optimized for speed or functionality; the default `dir` storage driver is slower and lacks fast snapshots, fast copy/launch, quotas, and optimized backups.

```bash
incus admin init --minimal

```

--------------------------------

### get_raw_nvram_var(guid, name)

Source: https://linuxcontainers.org/incus/docs/main/reference/instance_options

Gets a binary NVRAM variable.

```APIDOC
## get_raw_nvram_var(guid, name)

### Description
Gets a binary NVRAM variable.

### Parameters
- **guid** (string) - Required - The GUID of the variable.
- **name** (string) - Required - The name of the variable.

### Returns
- Binary value of the NVRAM variable.

### Notes
- Only available with EDK2 firmware.
```

--------------------------------

### incus config set examples

Source: https://linuxcontainers.org/incus/docs/main/reference/manpages/incus/config/set

Three examples show how to set a CPU limit, read cloud-init user-data from stdin, and set the HTTPS address for the server.

```bash
  incus config set [<remote>:]<instance> limits.cpu=2
      Will set a CPU limit of "2" for the instance.

  incus config set my-instance cloud-init.user-data - < cloud-init.yaml
      Sets the cloud-init user-data for instance "my-instance" by reading "cloud-init.yaml" through stdin.

  incus config set core.https_address=[::]:8443
      Will have the server listen on IPv4 and IPv6 port 8443.

```

--------------------------------

### Start Incus Windows VM with VGA console

Source: https://linuxcontainers.org/distrobuilder/docs/latest/_sources/tutorials/use.md.txt

Starts the configured `win10` VM and opens a VGA console for the graphical Windows installation.

```bash
incus start win10 --console=vga
```

--------------------------------

### Usage examples

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/network/create.md.txt

Three examples showing how to create a network named foo, create a network from a config file, and create an OVN network with an uplink.

```bash
  incus network create foo
      Create a new network called foo

  incus network create foo < config.yaml
      Create a new network called foo using the content of config.yaml.

  incus network create bar network=baz --type ovn
      Create a new OVN network called bar using baz as its uplink network
```

--------------------------------

### incus info examples

Source: https://linuxcontainers.org/incus/docs/main/reference/manpages/incus/info

Examples of using `incus info` to get instance information with `--show-log` and server information with `--resources`.

```bash
  incus info [<remote>:]<instance> [--show-log]
      For instance information.

  incus info [<remote>:] [--resources]
      For server information.

```

--------------------------------

### Create and start containers with incus-benchmark launch

Source: https://linuxcontainers.org/incus/docs/main/howto/benchmark_performance

Create and start containers in one step. Add --freeze to freeze each container right after it starts to measure pure launch times.

```bash
incus-benchmark launch --count 10 <image>

```

--------------------------------

### Examples of incus storage volume info

Source: https://linuxcontainers.org/incus/docs/main/_sources/reference/manpages/incus/storage/volume/info.md.txt

Two examples showing how to get state information for a custom volume and a virtual machine volume.

```bash
  incus storage volume info default foo
      Returns state information for a custom volume "foo" in pool "default"

  incus storage volume info default virtual-machine/v1
      Returns state information for virtual machine "v1" in pool "default"
```

--------------------------------

### Example output for importing to a VM

Source: https://linuxcontainers.org/incus/docs/main/_sources/howto/import_machines_to_instances.md.txt

Shows the interactive incus-migrate session for creating a virtual machine, including configuration overrides for CPU limits, storage pool size, and network.

```terminal
sudo ./bin.linux.incus-migrate
The local Incus server is the target [default=yes]:

What would you like to create?
1) Container
2) Virtual Machine
3) Virtual Machine (from .ova)
4) Custom Volume

Please enter the number of your choice: 2

Name of the new instance: foo
Please provide the path to a bootable disk, partition or image file: /path/to/disk.img
Do you want to enable secure boot? [default=no]:

Instance to be created:
  Name: foo
  Project: default
  Type: virtual-machine
  Source: /path/to/disk.img

Additional overrides can be applied at this stage:
1) Begin the migration with the above configuration
2) Override profile list
3) Set additional configuration options
4) Change instance storage pool or volume size
5) Change instance network

Please pick one of the options above [default=1]: 3
Please specify config keys and values (key=value ...): limits.cpu=2

Instance to be created:
  Name: foo
  Project: default
  Type: virtual-machine
  Source: /path/to/disk.img
  Config:
    limits.cpu: "2"

Additional overrides can be applied at this stage:
1) Begin the migration with the above configuration
2) Override profile list
3) Set additional configuration options
4) Change instance storage pool or volume size
5) Change instance network

Please pick one of the options above [default=1]: 4
Please provide the storage pool to use: default
Do you want to change the storage size? [default=no]: yes
Please specify the storage size: 20GiB

Instance to be created:
  Name: foo
  Project: default
  Type: virtual-machine
  Source: /path/to/disk.img
  Storage pool: default
  Storage pool size: 20GiB
  Config:
    limits.cpu: "2"

Additional overrides can be applied at this stage:
1) Begin the migration with the above configuration
2) Override profile list
3) Set additional configuration options
4) Change instance storage pool or volume size
5) Change instance network

Please pick one of the options above [default=1]: 5
Please specify the network to use for the instance: incusbr0

Instance to be created:
  Name: foo
  Project: default
  Type: virtual-machine
  Source: /path/to/disk.img
  Storage pool: default
  Storage pool size: 20GiB
  Network name: incusbr0
  Config:
    limits.cpu: "2"

Additional overrides can be applied at this stage:
1) Begin the migration with the above configuration
2) Override profile list
3) Set additional configuration options
4) Change instance storage pool or volume size
5) Change instance network

Please pick one of the options above [default=1]: 1
Instance foo successfully created
```

--------------------------------

### Install packages with cloud-init user-data

Source: https://linuxcontainers.org/incus/docs/main/cloud-init

Use the `packages` key to install specific packages during instance setup. Specify the package names as a list.

```yaml
config:
  cloud-init.user-data: |
    #cloud-config
    packages:
      - git
      - openssh-server

```
Tokens:
Raw