fix: add missing api_key field for custom provider in Dockerfile.hermes

The CMD script writes MODEL_API_KEY to .env as OPENAI_API_KEY but
does not include it in config.yaml's model section. Hermes with
provider: custom reads api_key from model.api_key in config.yaml,
not from OPENAI_API_KEY in .env. This causes 401 Authentication
Fails when users start a conversation inside the container.

Fix: add api_key field to the generated config.yaml model section.
This commit is contained in:
yuanrengu
2026-05-24 11:25:43 +08:00
parent be998adeb2
commit 69a95536ad
2 changed files with 9 additions and 1 deletions
+8
View File
@@ -4,6 +4,14 @@
---
## [Unreleased]
### 🐛 修复
- **Hermes Docker 镜像 `config.yaml` 缺少 `api_key` 字段**`Dockerfile.hermes` 的 CMD 脚本将 API Key 写入了 `.env``OPENAI_API_KEY`,但未写入 `config.yaml``model.api_key`,导致 `provider: custom` 时 Hermes 无法找到认证凭据(报 401 Authentication Fails)。现修复为在 `config.yaml``model` 段同步写入 `api_key: "${MODEL_API_KEY}"`
---
## [0.3.5] - 2026-05-15
### 🐛 修复