fix(docker): start Hermes Agent gateway in compose#385
Merged
outsourc-e merged 1 commit intomainfrom May 7, 2026
Merged
Conversation
The hermes-agent image's default entrypoint is the interactive CLI which exits immediately under `docker compose up -d`, causing the gateway to appear absent and the Workspace healthcheck/connection to fail with "Could not reach Hermes gateway". Override the command to `gateway run` so the long-running API/health server starts. Reproducible without this fix: a fresh `docker compose up -d` against upstream main fails with the symptoms reported in #360 across several users (different OSes), and the only working remedy was for users to manually patch their compose with `command: gateway run`. Closes #360
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
1 participant
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.
Summary
The
hermes-agentimage's default entrypoint is the interactive CLI, which exits immediately underdocker compose up -d. That makes the gateway appear absent and the Workspace healthcheck/connection fail withCould not reach Hermes gateway.This adds an explicit
command: [gateway, run]to thehermes-agentservice so the long-running API/health server starts onup -d.Closes #360.
Reproduction without this fix
Fresh
docker compose up -dagainst upstream main fails with the symptoms reported across several users on #360. The only working remedy was for users to manually patch their compose withcommand: gateway run(confirmed by @CipherFrame, @nazeshinjite, @nixbin-engineering in the issue thread).Test plan
docker compose down -v && docker compose up -d --force-recreatecurl http://localhost:8642/health→{"status":"ok","platform":"hermes-agent"}http://localhost:3000and confirm Workspace connects without "Could not reach Hermes gateway" error.