Bind-mount host ~/.hermes into hermes-webui container#50
Merged
Conversation
The WebUI image is a thin Python server that imports the hermes-agent
package in-process to serve /api/skills, /api/crons, /api/mcp/*, kanban,
and plugin visibility. Without the agent source on disk those endpoints
return 500 ModuleNotFoundError ('agent', 'cron', 'hermes_cli', 'tools').
Only chat completions and session data route through the gateway over
HTTP; everything else is read locally. Upstream's docker-compose.yml
mounts host ~/.hermes at /home/hermeswebui/.hermes for exactly this
reason — the WebUI's startup script finds <home>/hermes-agent and
pip-installs it into the container's venv.
Adds a required Hermes Home Host Path form field, bind-mounts it,
documents the why in description.md, bumps tipi_version 4 → 5.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the Hermes WebUI Runtipi app definition to require and bind-mount the host’s Hermes home directory into the container so the WebUI can import the hermes-agent Python package locally (enabling skills/crons/MCP/kanban/plugin visibility endpoints that otherwise fail).
Changes:
- Add a required “Hermes Home Host Path” form field to collect the host path to
~/.hermes. - Bind-mount that host path into the container at
/home/hermeswebui/.hermes. - Document why the mount is required and bump
tipi_version(4 → 5) with an updated timestamp.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| apps/hermes-webui/metadata/description.md | Documents the new required host mount and explains why WebUI needs local hermes-agent sources/config. |
| apps/hermes-webui/docker-compose.json | Adds a second volume mount from ${HERMES_HOME_HOST_PATH} to /home/hermeswebui/.hermes. |
| apps/hermes-webui/config.json | Adds the required form field for HERMES_HOME_HOST_PATH and increments tipi_version. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The WebUI image is a thin Python server that imports the hermes-agent package in-process to serve /api/skills, /api/crons, /api/mcp/*, kanban, and plugin visibility. Without the agent source on disk those endpoints return 500 ModuleNotFoundError ('agent', 'cron', 'hermes_cli', 'tools').
Only chat completions and session data route through the gateway over HTTP; everything else is read locally. Upstream's docker-compose.yml mounts host ~/.hermes at /home/hermeswebui/.hermes for exactly this reason — the WebUI's startup script finds /hermes-agent and pip-installs it into the container's venv.
Adds a required Hermes Home Host Path form field, bind-mounts it, documents the why in description.md, bumps tipi_version 4 → 5.