Project: lxd (Runtime / Container Runtime)
File: remotes.md

Remote servers are a concept in the Incus command-line client. By default, the command-line client interacts with the local Incus daemon, but you can add other servers or clusters to interact with. One use case for remote servers is to distribute images that can be used to create instances on local servers. See {ref}`image-servers` for more information. You can also add a full Incus server as a remote server to your client. In this case, you can interact with the remote server in the same way as with your local daemon. For example, you can manage instances or update the server configuration on the remote server. To be able to add an Incus server as a remote server, the server's API must be exposed, which means that its {config:option}`server-core:core.https_address` server configuration option must be set. When adding the server, you must then authenticate with it using the chosen method for {ref}`authentication`. See {ref}`server-expose` for more information. % Include parts of the content from file ```{include} howto/images_remote.md :start-after: <!-- Include start list remotes --> :end-before: <!-- Include end list remotes --> ``` % Include parts of the content from file ```{include} howto/images_remote.md :start-after: <!-- Include start add remotes --> :end-before: <!-- Include end add remotes --> ``` The Incus command-line client is pre-configured with the `local` remote, which is the local Incus daemon. To select a different remote as the default remote, enter the following command: incus remote switch <remote_name> To see which server is configured as the default remote, enter the following command: incus remote get-default You can configure remotes on a global, per-system basis. These remotes are available for every user of the Incus server for which you add the configuration. Users can override these system remotes (for example, by running or ), which results in the remote and its associated certificates being copied to the user configuration. To configure a global remote, create or edit a `config.yml` file that is located in `/etc/incus/`. Certificates for the remotes must be stored in the `servercerts` directory in the same location (for example, `/etc/incus/servercerts/`). They must match the remote name (for example, `foo.crt`). It's also possible to provide per-remote client certificates by placing them in the `clientcerts` directory. The similarly must match the remote name (for example, `foo.crt` and `foo.key`). See the following example configuration: ``` remotes: foo: addr: https://192.0.2.4:8443 auth_type: tls project: default protocol: incus public: false bar: addr: https://192.0.2.5:8443 auth_type: tls project: default protocol: incus public: false ``` (remote-keepalive)= For those frequently interacting with a particular remote, it's possible to enable a new `keepalive` mode. When enabled, Incus will maintain a connection with the target server for up to the configured timeout. This can significantly reduce the latency when running many `incus` commands. To enable, edit your `config.yml` (typically in `~/.config/incus`) and change your remote to look like: ``` my-remote: addr: https://192.0.2.5:8443 auth_type: tls project: default protocol: incus public: false keepalive: 30 ``` In this example, a timeout of 30 seconds will be used.