Academy → Using HermesOfficial documentation · clear explanation

Docker

Docker

Beginner35 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Docker as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Quick start, Running in gateway mode, Running the dashboard, then verify failure modes and version compatibility.

What do you need first?

No prior experience is required; follow the steps on a safe test setup first.

What will you know?

A clear outcome before you read.

  • Understand Docker without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

Gateway
The process that connects Hermes to channels such as Telegram or Discord and routes messages.
Official page description

Running Hermes Agent in Docker and using Docker as a terminal backend

Topic map

What does the source say, and in what order?

  1. 01
    Quick start

    Start here to understand the core idea or structure.

  2. 02
    Running in gateway mode

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Running the dashboard

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Running interactively (CLI chat)

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Persistent volumes

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Immutable install tree

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Multi-profile support

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Reaching more than one profile from outside the container

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Why one container with many profiles, not many containers

    Read this after the foundation, then connect it to the previous step.

  10. 10
    When you DO want a separate container

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

mkdir -p ~/.hermes docker run -it --rm \ -v ~/.hermes:/opt/data \ nousresearch/hermes-agent setup
docker run -d \ --name hermes \ --restart unless-stopped \ -v ~/.hermes:/opt/data \ -p 8642:8642 \ nousresearch/hermes-agent gateway run
tool_loop_guardrails: hard_stop_enabled: true hard_stop_after: exact_failure: 5 idempotent_no_progress: 5
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Docker” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?