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
+1 -1
View File
@@ -96,7 +96,7 @@ CMD ["bash", "-c", "\
export TDAI_LLM_MODEL=\"${MODEL_NAME}\" && \
export TDAI_LLM_BASE_URL=\"${MODEL_BASE_URL}\" && \
export TDAI_LLM_API_KEY=\"${MODEL_API_KEY}\" && \
printf \"model:\\n default: \\\"${MODEL_NAME}\\\"\\n provider: \\\"${MODEL_PROVIDER}\\\"\\n base_url: \\\"${MODEL_BASE_URL}\\\"\\n\\nmemory:\\n provider: memory_tencentdb\\n\" > \"$CFG\" && \
printf \"model:\\n default: \\\"${MODEL_NAME}\\\"\\n provider: \\\"${MODEL_PROVIDER}\\\"\\n base_url: \\\"${MODEL_BASE_URL}\\\"\\n api_key: \\\"${MODEL_API_KEY}\\\"\\n\\nmemory:\\n provider: memory_tencentdb\\n\" > \"$CFG\" && \
printf \"OPENAI_API_KEY=${MODEL_API_KEY}\\n\" > \"$ENVFILE\" && \
echo \"=== Config: model=${MODEL_NAME}, provider=${MODEL_PROVIDER}, url=${MODEL_BASE_URL} ===\" && \
echo \"=== Gateway starting... ===\" && \