Hermes Agent fails in Docker browser tools, focusing on Node.js version, browser dependencies, container permissions, and display environment. Chat availability does not mean browser automation is available, as browser links require additional system dependencies.
Confirm the underlying dependencies first
The official installation documentation mentions that Hermes relies on components such as Node.js v22, ripgrep, ffmpeg, and more. Browser automation and WhatsApp bridging are particularly dependent on the Node ecosystem. If your image is still an old node, you may encounter a deep dependency error instead of a clear "version is wrong".
Common causes in containers
- The mirror lacks the browser runbook, causing Playwright/Chromium to fail to start.
- Container security policies restrict sandboxes, and you need to configure permissions according to the image description.
- The working directory is not mounted correctly, and the browser fails to download the file or save the state.
- The network proxy is only configured on the host machine, and the web page access to the container fails.
Recommended investigation method
Go to the container first to perform minimal browser tests instead of directly letting Hermes run complex web tasks. After confirming that the node, browser, and network are all normal, return to the Hermes task. If you see errors related to browser, chromium, sandbox, and shared library in the logs, it is basically a container environment problem.
In the production environment, it is recommended to accept browser capabilities and ordinary chat capabilities separately: chat pass, tool pass, browser pass, and file mount pass, each layer is tested separately so that the subsequent agent tasks will not get stuck halfway.
