Will Hermes Compose Reuse the Setup State?
Mount the same host directory at /opt/data for setup and the Compose gateway. Check the resolved bind mount, then verify that an isolated replacement can read a known session.
Check the rendered mount before starting the gateway
Choose one absolute host directory for a disposable Hermes profile. Use it when running the setup wizard and mount it at /opt/data in the Compose service. Enable only the integrations needed for the trial, and record the image reference used by setup. Hermes documents stable tags and exact digest pins, so use the same verified digest for both phases when testing continuity. Render the Compose configuration locally and inspect the gateway mount's type, source, target, and write mode. A plausible-looking relative path can resolve to a different directory when the Compose project moves. For example, two directories named hermes-data can both be writable and still give you entirely different session histories. Compare the rendered source with the setup directory before starting with `docker compose up -d`. Keep any rendered environment values out of the test record.
Hermes Docker Setup | Hermes AgentTest the setup-to-gateway handoff with an observable fixture
Compose distinguishes the running service from its persistent storage. Use that distinction to test the handoff in a disposable project with a synthetic account or test channel. Before replacing the gateway through your usual Compose rollout, record its container ID and create a session containing a unique marker such as `mount-check-83`. Record the session identifier and verify that the marker is visible before the rollout. After replacement, confirm the container ID changed, reopen the recorded session, and verify the marker in its stored history. Then send a new test message and record whether a reply arrives. A visible marker with no fresh reply puts the next check on gateway or provider operation. A fresh reply with the old session missing calls for checking the mount and profile first. Both observations belong in the same handoff record.
How Compose works | Docker DocsDefine one service with an explicit state path
Use Docker Desktop if the host already runs it, or install the Compose plugin if you have Docker Engine and the Docker CLI on Linux. Put the deployment in a compose.yaml file with one service named hermes. Set the image to a selected stable release of nousresearch/hermes-agent and use the gateway startup from the upstream Docker guide. Choose a restart policy that matches how you expect the service to recover after host maintenance.
Set the service's volume source to the absolute path of the host directory used by the wizard, with /opt/data as its destination. Review the resolved source under the same account that will launch Compose. Keep one gateway pointed at that directory, especially if a single-container trial is already running.
How Compose works | Docker DocsProve that a replacement keeps the session
On a fresh host, run mkdir -p ~/.hermes, then docker run -it --rm -v ~/.hermes:/opt/data nousresearch/hermes-agent setup. Configure a model and one test channel. From the directory containing the Compose file, start the gateway with docker compose up -d. Check the service logs and send a test message. Record the session identifier or a distinctive message you can find in its history.
In an illustrative pilot, send a message containing the phrase cedar-41. During a maintenance window, run docker compose down followed by docker compose up -d. Check the earlier session for cedar-41, then send a fresh message and verify its reply. If the new reply succeeds but the old session is absent, compare the wizard and service mounts before accepting the deployment.
Hermes Docker Setup | Hermes AgentSet an acceptance test for browser access
For a channel-only deployment, leave dashboard access out of the Compose service. If an operator needs it, decide who should connect before publishing a port. The Hermes dashboard command defaults to 127.0.0.1 on port 9119. Inside Docker, the listener and the host-side port mapping are separate. For a private deployment, verify that the chosen private route reaches the service and that the host's public interface does not.
If the dashboard must be public, configure a supported authentication provider and test in a fresh browser session. Pass the check only if an unauthenticated visitor is prompted to sign in before seeing agent data and a valid operator can then open the dashboard. A connection failure calls for checking the listener and publication. A visible dashboard before sign-in calls for closing exposure and fixing authentication.
Hermes Web Dashboard | Hermes AgentKeep a known release and a state backup
Record the deployed image digest before changing it. The Hermes Docker guide distinguishes versioned stable tags from the moving stable and latest tags, and identifies a digest as the exact deployment reference. Back up the mounted state before an upgrade and record which image the backup came from. Include the Compose configuration so the operator can recover both the image selection and its mount settings.
After the upgrade, repeat the same session lookup and fresh channel reply used in the replacement test. If only the new release fails, use the recorded digest to identify the previous image. Check state compatibility before starting it against data already touched by the upgrade. If compatibility is uncertain, rehearse recovery with a copy of the pre-upgrade backup and separate test credentials.
Hermes Docker Setup | Hermes Agent