> For the complete documentation index, see [llms.txt](https://docs.clore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clore.ai/for-hosts/installing-clore-hosting/installing-clore-hosting-software.md). # Installing on HiveOS This page covers installation on **HiveOS**. For a standard Ubuntu server, see [Installing on Ubuntu](/for-hosts/installing-clore-hosting/installing-clore-hosting-ubuntu.md) — the install command is the same; only the OS preparation differs. ## Server Requirements The server (or rig – these terms are nearly interchangeable in this context) must be equipped with NVIDIA GPUs, as AMD is currently not supported. The minimum required disk space is 32 GB (at least 30 GB free on the system partition is recommended); for reliability, it's recommended to use an SSD instead of a flash drive. A minimum of 8 GB of RAM is required, but 16 GB will provide greater stability. As for the CPU, the system can work with a Celeron on a 1151 socket, but for more efficient performance, consider using a CPU like the i7-6700. Before proceeding, it is highly recommended to disable any overclocking, including the Power Limit (PL), and reset the GPUs to factory settings. Afterward, stress-test the system for stability by, for example, testing the GPUs using the kawpow algorithm and loading the CPU. Monitor temperatures and ensure everything is running stably. If the system operates stably and temperatures are within a safe range, continue to the next step in the instructions. If temperatures are too high or errors occur, address these issues first – for example, by improving cooling or troubleshooting – and ensure stable operation before proceeding. ## Recommended Drivers & CUDA (HiveOS) HiveOS includes its own driver management via the `nvidia-driver-update` command. For best compatibility with Clore.ai workloads (especially ML/AI), use the following recommended versions: ### NVIDIA Drivers | Branch | Version | CUDA Support | Recommended For | | --------------- | ---------- | --------------- | ---------------------------------------------------- | | **R580 (LTSB)** | 580.126.18 | Up to CUDA 12.8 | Most GPUs — stable, long-term support until Aug 2028 | | **R590** | 590.48.01 | Up to CUDA 13.1 | RTX 50 series (5090/5080), latest features | To install a specific version in HiveOS: ```bash nvidia-driver-update 580.126.18 --force ``` For RTX 50 series GPUs: ```bash nvidia-driver-update 590.48.01 --force ``` > **Important:** Do not use `nvidia-driver-update --force` without specifying a version — it may install an older default driver that doesn't support modern CUDA workloads. The installer itself does **not** install or upgrade GPU drivers — a working NVIDIA driver must be installed before you run it (`nvidia-smi` must work). ### CUDA Toolkit Compatibility Most renters use Docker images that include their own CUDA runtime, so hosts typically don't need to install the CUDA Toolkit manually. However, **the host's NVIDIA driver must support the CUDA version required by the renter's workload.** | CUDA Version | Minimum Driver | Status | | ------------ | -------------- | ----------------------------------- | | CUDA 12.4 | R550+ | Widely used in ML ecosystem | | CUDA 12.8 | R570+ | Latest stable 12.x branch | | CUDA 13.1 | R590+ | Latest, optimized for RTX 50 series | **Recommendation:** Install R580 LTSB (580.126.18) for broad compatibility with CUDA 12.x workloads. If you host RTX 50 series GPUs, use R590 (590.48.01) for full CUDA 13.x support. ## Preparing the Rig (HiveOS) ### 1. Open the rig's Shell in HiveOS Choose the rig in the HiveOS dashboard and open **Remote Access → Hive Shell Start** (or connect over SSH). ### 2. Update HiveOS ```bash hive-replace -y --stable ``` #### If HiveOS Disk Space Issues Arise If there's less free space on the disk than expected after installation or update (e.g., only 20 GB free on a 512 GB disk), execute the following: * **For M.2:** ```bash growpart /dev/nvme0n1 4 resize2fs /dev/nvme0n1p4 ``` * **For SATA:** ```bash growpart /dev/sda 4 resize2fs /dev/sda4 ``` ### 3. Run updates in sequence ```bash selfupgrade --force apt update apt upgrade apt autoremove ``` ### 4. Update the driver ```bash nvidia-driver-update 580.126.18 --force ``` For RTX 50 series GPUs, use version `590.48.01` or later. ### 5. Reboot the rig ```bash reboot ``` ## Installing the Hosting Agent Installation is one command, generated for you by the dashboard. The installer detects HiveOS automatically — the same command works on Ubuntu and HiveOS rigs alike. ### 1. Create the server on the website Go to [clore.ai](https://clore.ai/), register or log in, open [My Servers](https://clore.ai/my-servers) and click **Add Server**: * **Quick** — one command that installs the hosting agent **and** registers the machine to your account in one step, with default settings (max rental length 300 hours, USD autopricing at $5 per server per day for on-demand and spot) that you can adjust from the dashboard afterwards. * **Advanced** — name the server first, then copy its install and register commands (including a combined one-liner with the server's token) from the server page. To bring up many rigs at once, use the modal's **Mass** section instead — HiveOS fleets are onboarded through a flight sheet there; see [Clore Fleet (Mass onboarding)](/for-hosts/advanced/clore-fleet-mass-onboarding.md). To onboard a single rig through your linked HiveOS account, see [HiveOS Integration](/for-hosts/advanced/hiveos-integration.md). ### 2. Pick an installer channel | Channel | What it is | | ---------- | ---------------------------------------------------------------------------------- | | **Stable** | Recommended — thoroughly tested releases, updated less frequently | | **Beta** | Newest updates and features before they reach Stable — may be less reliable | | **Legacy** | Previous-generation installer — a fallback if Stable does not work on your machine | **Stable (recommended):** ```bash bash <(curl -s https://gitlab.com/cloreai-public/hosting-agent-installer/-/raw/main/install.sh) ``` **Beta:** ```bash bash <(curl -s https://gitlab.com/cloreai-public/hosting-agent-installer/-/raw/dev/install.sh) --channel beta ``` **Legacy:** ```bash bash <(curl -s https://gitlab.com/cloreai-public/hosting-agent-installer/-/raw/legacy/install.sh) ``` You can switch a running server between Stable and Beta updates later from its server page (requires an up-to-date hosting agent; not possible while the server is rented). ### 3. Run the install command as root ```bash sudo -i ``` (In Hive Shell you are usually already root.) Then paste the command copied from the dashboard. If you used the Advanced path, append the token shown on the server's page to install and register in one step: ```bash bash <(curl -s https://gitlab.com/cloreai-public/hosting-agent-installer/-/raw/main/install.sh) --init-token ``` If you ran the plain install command without a token, register the machine afterwards with: ```bash /opt/clore-hosting/clore.sh --init-token ``` The installer checks its prerequisites up front and tells you what is missing. It needs outbound access to the Docker and NVIDIA package repositories, GitHub, GitLab, Docker Hub, and `api.clore.ai` — see [Network Requirements](/for-hosts/installing-clore-hosting/network-requirements.md). ### 4. Finalize Reboot the rig, wait a moment, and refresh the My Servers page. If everything was set up correctly, the server will show as online. ```bash reboot ``` ## How to Disable All Installed Services If you need to disable everything previously installed: 1. Disable the services: ```bash systemctl disable clore-hosting.service systemctl disable docker.service systemctl disable docker.socket ``` 2. Reboot the system: ```bash reboot ``` ## How to Re-enable Services To re-enable the services: 1. Enable the services: ```bash systemctl enable clore-hosting.service systemctl enable docker.service systemctl enable docker.socket ``` 2. Reboot the system: ```bash reboot ``` ## Removing the Previously Installed Token To delete the token, use the command: ```bash /opt/clore-hosting/clore.sh --reset ``` The file containing the token is located at: ``` /opt/clore-hosting/client/auth ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.clore.ai/for-hosts/installing-clore-hosting/installing-clore-hosting-software.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.