Will Hermes Compose Reattach the Right State?
Use the official Hermes Compose recipe, pin the tested image by digest, and compare Docker’s mount records across a staging rebuild. Require the same writable state source before accepting the deployment.
Check storage identity before opening a session
Treat a Compose rebuild as a test of two independent inputs: the image reference and the state source. Keep the tested image digest in the deployment record, then inspect the container’s mounts before and after rebuilding a staging instance. For a bind mount, compare the resolved Docker host path that backs /opt/data. For a Docker-managed volume, compare the volume name on the same Docker host. A successful startup can coexist with a fresh state directory. For example, if the path changes from /srv/hermes/staging to /srv/hermes/default, reject the rebuild even if the gateway answers. After the mount check passes, open an existing synthetic session and verify a saved marker through Hermes. That second check exercises the application’s ability to read the state.
Hermes Docker Setup | Hermes AgentChoose storage by how you will recover it
Use a bind mount when the host backup job already covers an explicit directory and another operator can identify that directory from the deployment record. Use a named volume when the team prefers Docker to manage storage and the recovery runbook includes the volume name and an export and restore procedure. Test the distinction by asking a second operator to recover a synthetic session on a spare host using only the recorded deployment and backup. A same-host mount match says little about whether a usable backup exists elsewhere. Compare Compose with the alternative you would actually operate. For a workstation-only workflow, time a native recovery using the same acceptance checks. Skip DIY when the required restore coverage has no owner and an alternative can demonstrate it.
Volumes | Docker DocsSet up the state directory first
Decide where the gateway's state should live on the Docker host. Create a dedicated directory with access limited to the people and processes that need it. Hermes stores configuration, credentials, sessions, skills, and memories under the mounted directory. Start the official Hermes image interactively using the setup example in the Hermes Docker guide, with that directory mounted at /opt/data. Complete the wizard for the provider and channel you intend to test.
Use the same absolute host path in the Compose service and record the image release or digest beside it. Use a separate state directory for each independent gateway. Before starting Compose, verify that the setup wrote files under the intended host path. An empty directory or unexpected ownership is a reason to check the mount and permissions before proceeding.
Hermes Docker Setup | Hermes AgentVerify a reply after recreation
Build the service definition from the Hermes Docker guide for your selected release. Confirm that Compose uses the intended image, gateway startup settings, and host mount. Start the service with docker compose up and check its state with docker compose ps. A running service is the first check. The next is a fresh reply through the channel that will actually serve users.
In an illustrative trial, use one test channel and a harmless session marker, orchid-26. Record the session where you entered it, back up the state directory, and recreate the container with the same image and mount. Pass the test when the old session still contains the marker and the channel delivers exactly one reply to a fresh message. If the marker disappears, check the effective host path and the container's access to it.
How Compose works | Docker DocsTest dashboard access separately
Leave the dashboard unpublished if the team only needs a chat channel. For a private operator dashboard, follow the Hermes Docker guide's loopback and tunnel instructions, then test reachability from both the operator's machine and a machine outside the approved access path. Hermes defaults to port 9119 for its local dashboard. A dashboard listening beyond loopback requires an authentication provider.
If the dashboard must be reachable beyond loopback, configure supported authentication and check that an unauthenticated browser cannot view settings or sessions. Then sign in as an authorized operator and confirm the expected session opens. If the authorized test fails, check container binding and host port publishing before changing authentication. The deprecated insecure flag has no effect.
Hermes Web Dashboard | Hermes Agent