What Deployment is for
Docker appears in Hermes in two distinct roles. The whole agent can run inside a container, or the host agent can use Docker as its terminal backend. These choices affect where configuration, tools, files, and credentials live. For an unattended service, plan the persistent data location and recovery procedure before selecting an image. Keep the agent host separate from the website hosting decision; a static resource site does not require a full agent runtime in its web server.
What you need
- A compatible Docker host or another documented deployment environment, with adequate storage and operational access.
- A persistent data plan, protected credentials, and a clear network access policy for any administrative endpoints.
Set it up
- 1
Choose the deployment role and inspect the current official instructions for the installed release. Prefer an identified stable version for reproducibility.
- 2
Configure persistence, service startup, and backups deliberately. Begin without unnecessary public ports, then run a harmless agent task and restart test.
Check it works
- Verify that configuration and expected data survive a restart, and that an actual scheduled output appears.
- Confirm administrative endpoints are accessible only as intended and that logs identify a failing process clearly.
Limits and failure points
- A running container is not proof that the gateway, tools, model route, and delivery all work.
- Image channels differ. Local models, browser runtimes, retained logs, and container images can consume substantial storage beyond a small website project.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.