Hide navigation sidebar
Hide table of contents sidebar
Back to top
Toggle table of contents sidebar

# How to manage instances

When listing the existing instances, you can see their type, status, and location (if applicable). You can filter the instances and display only the ones that you are interested in.

Enter the following command to list all instances:

    incus list

You can filter the instances that are displayed, for example, by type, status or the cluster member where the instance is located:

    incus list type=container
    incus list status=running
    incus list location=server1

You can also filter by name. To list several instances, use a regular expression for the name. For example:

    incus list ubuntu.*

Enter `incus list --help` to see all filter options.

Query the `/1.0/instances` endpoint to list all instances. You can use Recursion to display more information about the instances:

    incus query /1.0/instances?recursion=2

You can filter the instances that are displayed, by name, type, status or the cluster member where the instance is located:

    incus query /1.0/instances?filter=name+eq+ubuntu
    incus query /1.0/instances?filter=type+eq+container
    incus query /1.0/instances?filter=status+eq+running
    incus query /1.0/instances?filter=location+eq+server1

To list several instances, use a regular expression for the name. For example:

    incus query /1.0/instances?filter=name+eq+ubuntu.*

See `GET /1.0/instances` for more information.

## Show information about an instance

Enter the following command to show detailed information about an instance:

    incus info <instance_name>

Add `--show-log` to the command to show the latest log lines for the instance:

    incus info <instance_name> --show-log

Query the following endpoint to show detailed information about an instance:

    incus query /1.0/instances/<instance_name>

See `GET /1.0/instances/{name}` for more information.

## Start an instance

Enter the following command to start an instance:

    incus start <instance_name>

You will get an error if the instance does not exist or if it is running already.

To immediately attach to the console when starting, pass the `--console` flag. For example:

    incus start <instance_name> --console

See How to access the console for more information.

To start an instance, send a PUT request to change the instance state:

    incus query --request PUT /1.0/instances/<instance_name>/state --data '{"action":"start"}'

The return value of this query contains an operation ID, which you can use to query the status of the operation:

    incus query /1.0/operations/<operation_ID>

Use the following query to monitor the state of the instance:

    incus query /1.0/instances/<instance_name>/state

See `GET /1.0/instances/{name}/state` and `PUT /1.0/instances/{name}/state`for more information.

## Stop an instance

Enter the following command to stop an instance:

    incus stop <instance_name>

You will get an error if the instance does not exist or if it is not running.

To stop an instance, send a PUT request to change the instance state:

    incus query --request PUT /1.0/instances/<instance_name>/state --data '{"action":"stop"}'

The return value of this query contains an operation ID, which you can use to query the status of the operation:

    incus query /1.0/operations/<operation_ID>

Use the following query to monitor the state of the instance:

    incus query /1.0/instances/<instance_name>/state

See `GET /1.0/instances/{name}/state` and `PUT /1.0/instances/{name}/state`for more information.

## Delete an instance

If you don’t need an instance anymore, you can remove it. The instance must be stopped before you can delete it.

Enter the following command to delete an instance:

    incus delete <instance_name>

To delete an instance, send a DELETE request to the instance:

    incus query --request DELETE /1.0/instances/<instance_name>

See `DELETE /1.0/instances/{name}` for more information.

Caution

This command permanently deletes the instance and all its snapshots.

### Prevent accidental deletion of instances

There are different ways to prevent accidental deletion of instances:

- To protect a specific instance from being deleted, set `security.protection.delete` to `true` for the instance. See How to configure instances for instructions.

- In the CLI client, you can create an alias to be prompted for approval every time you use the `incus delete` command:

       incus alias add delete "delete -i"

## Rebuild an instance

If you want to wipe and re-initialize the root disk of your instance but keep the instance configuration, you can rebuild the instance.

Rebuilding is only possible for instances that do not have any snapshots.

Stop your instance before rebuilding it.

Enter the following command to rebuild the instance with a different image:

    incus rebuild <image_name> <instance_name>

Enter the following command to rebuild the instance with an empty root disk:

    incus rebuild <instance_name> --empty

For more information about the `rebuild` command, see `incus rebuild --help`.

To rebuild the instance with a different image, send a POST request to the instance’s `rebuild` endpoint. For example:

    incus query --request POST /1.0/instances/<instance_name>/rebuild --data '{"source": {"alias":"<image_alias>","server":"<server_URL>", protocol:"simplestreams"}}'

To rebuild the instance with an empty root disk, specify the source type as `none`:

    incus query --request POST /1.0/instances/<instance_name>/rebuild --data '{"source": {"type":"none"}}'

See `POST /1.0/instances/{name}/rebuild` for more information.