Bug Description
I have been running hermes agent in docker container for a while. Everything worked fine until I pulled the latest docker image v2026.4.23. When starting the agent, I received the following error:
chown: changing ownership of '/opt/data/config.yaml': Operation not permitted
The permission issue is linked with UID and GID that starts the container. My .hermes folder is owned by the same user that starts the container because I used -u $(id -u):$(id -g) in the startup script. This allows both the agent and user to access the folder, and works fine with v2026.4.16 and earlier.
In the new docker image v2026.4.23, I would receive that permission error with the same script. If I change the script to use -u 0:0, the container will start and the agent will run, but the .hermes folder owner is changed to 10000:10000, which now prevents the user to access .hermes folder in the terminal.
Is there a way to fix this problem so that the old way, i.e, -u $(id -u):$(id -g) continue to work with the new version ? Thanks.
Steps to Reproduce
Make sure the .hermes folder belongs to the user with permission 700 or even 755
docker run -it --rm -u $(id -u):$(id -g) --name hermes -v ~/.hermes:/opt/data nousresearch/hermes-agent:v2026.4.16 setup would work fine, but docker run -it --rm -u $(id -u):$(id -g) --name hermes -v ~/.hermes:/opt/data nousresearch/hermes-agent:v2026.4.23 setup will give the error message
chown: changing ownership of '/opt/data/config.yaml': Operation not permitted
Expected Behavior
Both versions of the images should work when starting with the -u $(id -u):$(id -g).
Actual Behavior
with -u 0:0 to start the container, it will modify the ownership of .hermes folder and make it inaccessible to user via terminal.
Affected Component
Other
Messaging Platform (if gateway-related)
No response
Debug Report
Cannot generate this as it won't start.
Operating System
NVIDIA DGX OS
Python Version
3.12.3
Hermes Version
not sure, using docker image
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
I have been running hermes agent in docker container for a while. Everything worked fine until I pulled the latest docker image v2026.4.23. When starting the agent, I received the following error:
chown: changing ownership of '/opt/data/config.yaml': Operation not permitted
The permission issue is linked with UID and GID that starts the container. My .hermes folder is owned by the same user that starts the container because I used -u$(id -u):$ (id -g) in the startup script. This allows both the agent and user to access the folder, and works fine with v2026.4.16 and earlier.
In the new docker image v2026.4.23, I would receive that permission error with the same script. If I change the script to use -u 0:0, the container will start and the agent will run, but the .hermes folder owner is changed to 10000:10000, which now prevents the user to access .hermes folder in the terminal.
Is there a way to fix this problem so that the old way, i.e, -u$(id -u):$ (id -g) continue to work with the new version ? Thanks.
Steps to Reproduce
Make sure the .hermes folder belongs to the user with permission 700 or even 755
docker run -it --rm -u $(id -u):$(id -g) --name hermes -v ~/.hermes:/opt/data nousresearch/hermes-agent:v2026.4.16 setupwould work fine, butdocker run -it --rm -u $(id -u):$(id -g) --name hermes -v ~/.hermes:/opt/data nousresearch/hermes-agent:v2026.4.23 setupwill give the error messagechown: changing ownership of '/opt/data/config.yaml': Operation not permitted
Expected Behavior
Both versions of the images should work when starting with the -u$(id -u):$ (id -g).
Actual Behavior
with -u 0:0 to start the container, it will modify the ownership of .hermes folder and make it inaccessible to user via terminal.
Affected Component
Other
Messaging Platform (if gateway-related)
No response
Debug Report
Cannot generate this as it won't start.Operating System
NVIDIA DGX OS
Python Version
3.12.3
Hermes Version
not sure, using docker image
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?