> 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/clore.ai/clore.ai-eng-zh/mian-xiang-zhu-ji-fang/server-offline-on-clore.ai/docker-failure.md).
# Docker 故障
**问题**\
Clore.ai 将矿机标记为 *Docker 故障* 并保持其离线状态，尽管 HiveOS 正在运行。
**症状**
* Clore 面板中显示“Docker 故障”图标。
* 在 **我的服务器** 部分中，GPU 显示为 *0x 未知* 或 GPU 数量不断变化。
***
**原因 1：GPU 或延长线不稳定**
如果 GPU 断开连接或不稳定，Clore 无法初始化它。\
即使 HiveOS 能看到 GPU，Clore 也无法使用它 → **Docker 故障**.
**解决方案：重启并检查硬件**
1. 检查 GPU 或延长线，确保一切连接牢固。
2. 重启矿机：
```
重启
```
重启后如果错误再次出现，问题很可能出在 GPU、主板或延长线上。
***
#### 原因 2：Python 环境损坏（Miniconda）
如果目录 `/opt/clore-hosting/miniconda-env` 已损坏，Clore 会在启动时卡住。
**解决方案：删除该环境并重启**
```
sudo systemctl stop clore-hosting.service
sudo rm -rf /opt/clore-hosting/miniconda-env
sudo systemctl start clore-hosting.service
```
***
#### 原因 3：依赖安装卡住
如果 Clore 无法启动，可能是因为依赖安装卡住了（例如 aiofiles、docker 等）。
**解决方案：重新安装依赖**
```
sudo /opt/clore-hosting/clore.sh --reinstall
```
***
#### 原因 4：安装了不稳定的 Docker 版本（例如 28.\*）
推荐版本： **27.5.1**\
Docker 28+ 很容易崩溃。
**解决方案：降级 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
```
***
#### 原因 5：所需服务未在启动时启用
重启后，系统不会启动 Docker 和 Clore Hosting → 服务器离线。
**解决方案：启用开机启动服务**
```
sudo systemctl enable clore-hosting.service
sudo systemctl enable docker.service
sudo systemctl enable docker.socket
```
***
#### 原因 6：驱动无法检测到 GPU（`nvidia-smi → 未找到设备`)
如果 HiveOS 无法检测到 GPU，Clore 就无法使用它 → 导致 Docker 故障。
**解决方案：重新安装驱动**
```
nvidia-driver-update 580.126.18 --force
```
***
#### 如果问题仍然存在——请将服务器从 Clore 中完全移除，更换令牌，然后重新添加。
如果内部配置损坏，这通常会有帮助。
***
**Docker 故障** 几乎总是意味着 **Clore 看不到 GPU**.\ 在 **90% 的情况下**，原因要么是服务被禁用，要么是 GPU/延长线不稳定。\ 解决根本问题，启用开机启动服务——你的矿机就会保持在线。
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.clore.ai/clore.ai/clore.ai-eng-zh/mian-xiang-zhu-ji-fang/server-offline-on-clore.ai/docker-failure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.