Hermes BibleUnofficial Docs
← All docs Docs / Using Hermes

Docker

Hermes Agent — Docker There are two distinct ways Docker intersects with Hermes Agent: 1. Running Hermes IN Docker — the agent itself runs inside a container (t

Using Hermes
Section
Using Hermes
Source
hermesbible.com/docs/user-guide/docker

Hermes Agent — Docker There are two distinct ways Docker intersects with Hermes Agent: 1. Running Hermes IN Docker — the agent itself runs inside a container (t

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Quick start
  2. Running in gateway mode
  3. Running the dashboard
  4. Running interactively (CLI chat)
  5. Persistent volumes
  6. Multi-profile support
  7. Reaching more than one profile from outside the container
  8. Why one container with many profiles, not many containers
  9. When you DO want a separate container
  10. Where the logs go
  11. Environment variable forwarding
  12. Docker Compose example
  13. Optional: Linux desktop audio bridge
  14. Resource limits

Section map

Quick start

Maps quick start to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Running in gateway mode

Maps running in gateway mode to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Running the dashboard

Maps running the dashboard to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Running interactively (CLI chat)

Maps running interactively (cli chat) to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Persistent volumes

Maps persistent volumes to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Multi-profile support

Maps multi-profile support to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Reaching more than one profile from outside the container

Maps reaching more than one profile from outside the container to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Why one container with many profiles, not many containers

Maps why one container with many profiles, not many containers to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Using Hermes doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Quick start, Running in gateway mode, Running the dashboard, Running interactively (CLI chat), Persistent volumes. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: docker, there, distinct, intersects, running. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitUsing Hermes documentation

Use when you need orientation for docker before applying exact upstream commands.

Verify firstQuick start

Open the source anchor for Quick start and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Using Hermes, then open the linked source page for exact current syntax.
  2. Start with the source section for Quick start; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Running in gateway mode if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Docker There are two distinct ways Docker intersects with Hermes Agent
  • 1. Running Hermes IN Docker
  • the agent itself runs inside a container (t

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page