# Docker Failure

**Problem**\
Clore.ai marks the rig as *Docker Failure* and keeps it offline, even though HiveOS is running.

**Symptoms**

* A “Docker Failure” icon is shown in the Clore panel.
* In the **My Servers** section, GPUs are displayed as *0x Unknown* or the GPU count keeps changing.

***

**Cause 1: Unstable GPU or Riser**

Clore cannot initialize a GPU if it's disconnected or unstable.\
Even if HiveOS sees the GPU, Clore can’t use it → **Docker Failure**.

**Solution: Restart and Check Hardware**

1. Check the GPU or riser, make sure everything is securely connected.
2. Reboot the rig:

```
reboot
```

If the error returns after reboot, the issue is likely with the GPU, motherboard, or risers.

***

#### Cause 2: Corrupted Python Environment (Miniconda)

Clore hangs on startup if the directory `/opt/clore-hosting/miniconda-env` is corrupted.

**Solution: Remove the environment and restart**

```
sudo systemctl stop clore-hosting.service
sudo rm -rf /opt/clore-hosting/miniconda-env
sudo systemctl start clore-hosting.service
```

***

#### Cause 3: Dependency installation is stuck

If Clore doesn't start, it may be due to a frozen installation of dependencies (e.g. aiofiles, docker, etc.).

**Solution: Reinstall dependencies**

```
sudo /opt/clore-hosting/clore.sh --reinstall
```

***

#### Cause 4: Unstable Docker version installed (e.g., 28.\*)

Recommended version: **27.5.1**\
Crashes are common with Docker 28+.

**Solution: Downgrade Docker**

```bash
sudo apt install \
docker-ce=5:27.5.1-1~ubuntu.22.04~jammy \
docker-ce-cli=5:27.5.1-1~ubuntu.22.04~jammy \
containerd.io -y
```

***

#### Cause 5: Required services are not enabled on startup

After reboot, the system doesn't launch Docker and Clore Hosting → server goes offline.

**Solution: Enable services on startup**

```
sudo systemctl enable clore-hosting.service
sudo systemctl enable docker.service
sudo systemctl enable docker.socket
```

***

#### Cause 6: Driver doesn't detect GPUs (`nvidia-smi → No devices found`)

If HiveOS doesn't detect the GPU, Clore can't work with it → results in Docker Failure.

**Solution: Reinstall the driver**

```
nvidia-driver-update --force
```

***

#### If the issue persists — fully remove the server from Clore, change the token, and re-add it.

This often helps if internal configs are broken.

***

<mark style="color:blue;">**Docker Failure**</mark> <mark style="color:blue;"></mark><mark style="color:blue;">almost always means that</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Clore doesn't see the GPU**</mark><mark style="color:blue;">.</mark>\ <mark style="color:blue;">In</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**90% of cases**</mark><mark style="color:blue;">, the cause is either a disabled service or an unstable GPU/risers.</mark>\ <mark style="color:blue;">Fix the root issue, enable services on startup — and your rig will stay online.</mark>


---

# Agent Instructions: 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:

```
GET https://docs.clore.ai/for-hosts/server-offline-on-clore.ai/docker-failure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.