dense sparrow
I am trying to run on MacOS with podman as the container host. I'm unable to even start hermes because it wants ownsership of the .hermes directory but can't obtain it. Is there a way around this?
docker run -it --rm \
-v ~/.hermes:/opt/data \
nousresearch/hermes-agent setup
/opt/data is not owned by 10000, fixing
chown: changing ownership of '/opt/data': Operation not permitted
Thanks!
shrewd parrot
@fathom summit
fathom summit
I am trying to run on MacOS with podman as the container host. I'm unable to eve...
Ha, yeah, that was a recent change added that also caused me some pain. I think there's an environment variable override you can use - USER_GUID and GROUP_GUID. If those match your host user/group IDs it should work. Let me know how you go with it!
dense sparrow
Thanks, I’ll give it a shot this evening!
fathom summit
Ah, sorry, it's HERMES_UID and HERMES_GID - just checked the source
Hopefully that'll get it working
dense sparrow
Ah, sorry, it's `HERMES_UID` and `HERMES_GID` - just checked the source
thanks! Seems like progress. Now I'm getting
Changing hermes UID to 501
Changing hermes GID to 20
groupmod: GID '20' already exists
i guess that means that the group already exists in the container image?
fathom summit
i guess that means that the group already exists in the container image?
Not necessarily, it's just overriding the script that fiddles with permissions
dense sparrow
it still doesn't start successfully though unfortunately.
fathom summit
it still doesn't start successfully though unfortunately.
Dang. Can you show me the logs from the container?
dense sparrow
dense sparrow
Dang. Can you show me the logs from the container?
that's all i get.
fathom summit
Huh
Not at my computer right now, but I'll see what I can do with I get back. I suspect the permissions on your volume are wonky though.
dense sparrow
I did try recreating the folder a few times.
fathom summit
With a completely new .hermes directory?
peak girder
It should find podman now
Done. PR #10066 is up.
Here's what went in (4 files, +96/-11):
**`tools/environments/docker.py`** — `find_docker()` now has a 4-step resolution chain:
1. `HERMES_DOCKER_BINARY` env var (explicit override, e.g. `/usr/bin/podman`)
2. `docker` on PATH
3. `podman` on PATH (automatic fallback)
4. macOS Docker Desktop known locations
**`docker/entrypoint.sh`** — Three fixes for rootless Podman on macOS:
- `HERMES_HOME="${HERMES_HOME:-/opt/data}"` instead of hardcoding
- `groupmod -o -g` tolerates non-unique GIDs (the macOS GID 20 "staff" collision)
- `chown` is best-effort with a warning instead of a hard failure
**Tests** — 5 new tests covering env var override, invalid/nonexistent override fallthrough, podman-when-docker-missing, and docker-preferred-over-podman.
This should unblock the Discord user's immediate problem. The more comprehensive Podman PRs (#8158, #8391) can be evaluated separately for deeper integration.
looks like this works as long as the folder has 777 permissions.