Running Hermes Agent in Docker can limit access, but logs may still fail
Installing directly on the host gives it broad access to the machine, which can feel too open for regular use. Running inside Docker is a way to choose exactly what it can access.
The setup had trouble connecting the Docker web UI and dashboard to a Hermes install running on the host. The current problem is that the web UI or dashboard cannot read Docker logs.
The container has `/var/run/docker.sock` mounted at `/var/run/docker.sock`, but still says it cannot read the Docker logs. The shown setup includes a container, a Hermes dashboard container, a shared Hermes , an `/opt/dockge` folder mount, the mount, and such as `HERMES_HOME`, `HERMES_UID`, and `HERMES_GID`.
Key points
- A host install gives broad machine access, which may be more than desired.
- Running in Docker can help limit what it can reach.
- Mounting `/var/run/docker.sock` alone did not make Docker logs readable.
- The web UI, dashboard, and agent may not be looking at the same runtime environment.
- Docker log access may depend on user , socket access, and where the agent actually runs.