Bug Description
hermes update cannot work fine in a container
Steps to Reproduce
- run
hermes update in a non-hermes-agent-published container
Expected Behavior
hermes update can work fine.
Actual Behavior
➜ ~ hermes update
✗ ``hermes update`` doesn't apply inside the Docker container.
Hermes Agent runs as a published image (nousresearch/hermes-agent), not a
git checkout — the container has no working tree to pull into. Update by
pulling a fresh image and restarting your container instead:
docker pull nousresearch/hermes-agent:latest
# then restart whatever started the container, e.g.:
docker compose up -d --force-recreate hermes-agent
# or, for ad-hoc runs, exit the current container and `docker run` again
Verify the new version after restart:
docker run --rm nousresearch/hermes-agent:latest --version
Notes:
• If you pinned a specific tag (e.g. ``:v0.14.0``) the ``:latest`` tag
won't move your container — pull the newer tag you actually want, or
switch to ``:latest`` / ``:main`` for rolling updates. See available
tags at https://hub.docker.com/r/nousresearch/hermes-agent/tags
• Your config and session history live under ``$HERMES_HOME`` (``/opt/data``
in the container, typically bind-mounted from the host) and persist
across image upgrades — re-pulling doesn't lose any state.
• Running a fork? Build your own image with this repo's ``Dockerfile``
and replace the ``docker pull`` step with your build/push pipeline.
Affected Component
CLI (interactive chat)
Messaging Platform (if gateway-related)
N/A (CLI only)
Debug Report
Report https://paste.rs/nxuMN
agent.log https://paste.rs/sehoY
gateway.log https://paste.rs/o2djV
Operating System
Ubuntu 24.04
Python Version
3.11.15
Hermes Version
v0.15.1 (2026.5.29)
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?
Bug Description
hermes update cannot work fine in a container
Steps to Reproduce
hermes updatein a non-hermes-agent-published containerExpected Behavior
hermes updatecan work fine.Actual Behavior
➜ ~ hermes update ✗ ``hermes update`` doesn't apply inside the Docker container. Hermes Agent runs as a published image (nousresearch/hermes-agent), not a git checkout — the container has no working tree to pull into. Update by pulling a fresh image and restarting your container instead: docker pull nousresearch/hermes-agent:latest # then restart whatever started the container, e.g.: docker compose up -d --force-recreate hermes-agent # or, for ad-hoc runs, exit the current container and `docker run` again Verify the new version after restart: docker run --rm nousresearch/hermes-agent:latest --version Notes: • If you pinned a specific tag (e.g. ``:v0.14.0``) the ``:latest`` tag won't move your container — pull the newer tag you actually want, or switch to ``:latest`` / ``:main`` for rolling updates. See available tags at https://hub.docker.com/r/nousresearch/hermes-agent/tags • Your config and session history live under ``$HERMES_HOME`` (``/opt/data`` in the container, typically bind-mounted from the host) and persist across image upgrades — re-pulling doesn't lose any state. • Running a fork? Build your own image with this repo's ``Dockerfile`` and replace the ``docker pull`` step with your build/push pipeline.Affected Component
CLI (interactive chat)
Messaging Platform (if gateway-related)
N/A (CLI only)
Debug Report
Operating System
Ubuntu 24.04
Python Version
3.11.15
Hermes Version
v0.15.1 (2026.5.29)
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?