Hermes/ayon-mcp
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Docker deployment fragile: network, DNS, API key rot #3

New Issue
Open
opened 2026-07-16 12:40:54 +00:00 by Hermes · 0 comments
Hermes commented 2026-07-16 12:40:54 +00:00
Owner
Copy Link
Copy Source

Problem

The MCP container deployment requires manual intervention after every restart:

  1. Docker network not persistent — docker network connect ayon-private_default mcp-ayon is lost on every container recreate. DNS resolution for ayon-private-server-1 does not work cross-network, forcing hardcoded IP (192.168.64.4) in .env.
  2. API key rot — Stored in .env, can be silently invalidated or corrupted (observed: key became *** in file after Hermes secret redaction). Requires manual key regeneration via AYON WebUI.
  3. Wrong AYON instance detection — MCP was configured to use original instance (port 5000, ayon-docker_default network) instead of the private clone (port 5001, ayon-private_default network). This was silently failing.

Impact

Every MCP restart costs 5-10 manual fix steps before publishing works.

Proposed Fix

  • Declare ayon-private_default as external network in compose.yml with health checks
  • Use Docker secrets or a config volume instead of .env for the API key
  • Add a startup check that validates the API key against the configured AYON instance and fails fast with a clear error
## Problem The MCP container deployment requires manual intervention after every restart: 1. **Docker network not persistent** — `docker network connect ayon-private_default mcp-ayon` is lost on every container recreate. DNS resolution for `ayon-private-server-1` does not work cross-network, forcing hardcoded IP (192.168.64.4) in `.env`. 2. **API key rot** — Stored in `.env`, can be silently invalidated or corrupted (observed: key became `***` in file after Hermes secret redaction). Requires manual key regeneration via AYON WebUI. 3. **Wrong AYON instance detection** — MCP was configured to use original instance (port 5000, `ayon-docker_default` network) instead of the private clone (port 5001, `ayon-private_default` network). This was silently failing. ## Impact Every MCP restart costs 5-10 manual fix steps before publishing works. ## Proposed Fix - Declare `ayon-private_default` as external network in compose.yml with health checks - Use Docker secrets or a config volume instead of `.env` for the API key - Add a startup check that validates the API key against the configured AYON instance and fails fast with a clear error
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Niklas Hermes
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Hermes/ayon-mcp#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?