### Install Incus Source: https://github.com/zabbly/incus/blob/daily/README.md Updates the package list and installs the Incus package after a repository has been added. This command should be run as root. ```sh apt-get update apt-get install incus ``` -------------------------------- ### Add Incus Stable Repository Source: https://github.com/zabbly/incus/blob/daily/README.md Configures the apt package manager to include the Incus stable repository. This enables the installation of the latest stable release of Incus. ```sh sh -c 'cat < /etc/apt/sources.list.d/zabbly-incus-stable.sources Enabled: yes Types: deb URIs: https://pkgs.zabbly.com/incus/stable Suites: $(. /etc/os-release && echo ${VERSION_CODENAME}) Components: main Architectures: $(dpkg --print-architecture) Signed-By: /etc/apt/keyrings/zabbly.asc EOF' ``` -------------------------------- ### Add Incus LTS 6.0 Repository Source: https://github.com/zabbly/incus/blob/daily/README.md Configures the apt package manager to include the Incus 6.0 LTS repository. This allows installation of Incus 6.0.x versions on compatible Ubuntu and Debian systems. ```sh sh -c 'cat < /etc/apt/sources.list.d/zabbly-incus-lts-6.0.sources Enabled: yes Types: deb URIs: https://pkgs.zabbly.com/incus/lts-6.0 Suites: $(. /etc/os-release && echo ${VERSION_CODENAME}) Components: main Architectures: $(dpkg --print-architecture) Signed-By: /etc/apt/keyrings/zabbly.asc EOF' ``` -------------------------------- ### Commit Sign-off Example Source: https://github.com/zabbly/incus/blob/daily/CONTRIBUTING.md A valid sign-off line is required for all contributions to the Incus project. This line certifies that the author wrote the code or has the right to pass it on as an open-source contribution. It must include the author's real name and a valid email address. ```APIDOC Signed-off-by: Random J Developer ``` -------------------------------- ### Incus Package Information Source: https://github.com/zabbly/incus/blob/daily/README.md Provides details about the available Incus packages from Zabbly repositories. ```APIDOC Incus Packages: - incus: The main Incus package. - incus-client: Contains only the Incus CLI tool for remote management. - incus-ui-canonical: A rebranded LXD web interface for Incus. ``` -------------------------------- ### Add Incus Daily Repository Source: https://github.com/zabbly/incus/blob/daily/README.md Configures the apt package manager to include the Incus daily build repository. This is for accessing the latest, potentially untested, daily builds of Incus. ```sh sh -c 'cat < /etc/apt/sources.list.d/zabbly-incus-daily.sources Enabled: yes Types: deb URIs: https://pkgs.zabbly.com/incus/daily Suites: $(. /etc/os-release && echo ${VERSION_CODENAME}) Components: main Architectures: $(dpkg --print-architecture) Signed-By: /etc/apt/keyrings/zabbly.asc EOF' ``` -------------------------------- ### Configure Incus UI Listener Source: https://github.com/zabbly/incus/blob/daily/README.md Sets the Incus configuration to listen on a specific port for network access, which is required for using the Incus UI. This command should be run as root. ```sh incus config set core.https_address :8443 ``` -------------------------------- ### Import GPG Key for Package Verification Source: https://github.com/zabbly/incus/blob/daily/README.md Imports the Zabbly public GPG key to verify the integrity of Incus packages. This involves fetching the key and displaying its fingerprint for manual verification against the expected fingerprint. ```sh curl -fsSL https://pkgs.zabbly.com/key.asc | gpg --show-keys --fingerprint ``` ```sh wget -q -O - https://pkgs.zabbly.com/key.asc | gpg --show-keys --fingerprint ``` -------------------------------- ### Save GPG Key Locally Source: https://github.com/zabbly/incus/blob/daily/README.md Saves the Zabbly public GPG key to the apt keyrings directory for package authentication. This step is crucial before adding repositories to ensure package authenticity. ```sh mkdir -p /etc/apt/keyrings/ curl -fsSL https://pkgs.zabbly.com/key.asc -o /etc/apt/keyrings/zabbly.asc ``` ```sh mkdir -p /etc/apt/keyrings/ wget -O /etc/apt/keyrings/zabbly.asc https://pkgs.zabbly.com/key.asc ``` -------------------------------- ### Developer Certificate of Origin (DCO) 1.1 Source: https://github.com/zabbly/incus/blob/daily/CONTRIBUTING.md The Developer Certificate of Origin (DCO) is a legal document that certifies the origin and licensing rights of a software contribution. It ensures that contributors have the right to submit their code under the project's open-source license. This version is DCO 1.1. ```APIDOC Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 660 York Street, Suite 102, San Francisco, CA 94110 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.