Gateway wasn't running CLI commands / errors in Docker
Thank you community for your help.
Setup was working fine on 2026.02.15 using docker on a VM. Updated to 2026.02.21 and how the gateway agent says it can't execute commands. Specifically, I'm asking it to edit a cron prompt (that it created originally) but the agent is telling me: "I still cannot run node dist/index.js ... myself because I cannot execute commands inside your gateway container from this chat runtime."
As context: docker compose exec openclaw-gateway node dist/index.js cron list works just fine.
After troubleshooting, I found now exec tools existed in the config json. Something I did must over overwritten the config.json (maybe the version upgrade). In any case, I manually overrode from the command line:
clawdock-exec node dist/index.js config set tools.exec.host gateway
clawdock-exec node dist/index.js config set tools.exec.ask off
clawdock-exec node dist/index.js config set tools.exec.security full
So my question:
1) Was that the right approach to "fix" the issue that the agent could not longer execute commands? Doctor --repair on the gateway was unhelpful
2) security audit --deep seems fine but is that the right config to allow the agent to run itself without huge security gaps?
Setup was working fine on 2026.02.15 using docker on a VM. Updated to 2026.02.21 and how the gateway agent says it can't execute commands. Specifically, I'm asking it to edit a cron prompt (that it created originally) but the agent is telling me: "I still cannot run node dist/index.js ... myself because I cannot execute commands inside your gateway container from this chat runtime."
As context: docker compose exec openclaw-gateway node dist/index.js cron list works just fine.
After troubleshooting, I found now exec tools existed in the config json. Something I did must over overwritten the config.json (maybe the version upgrade). In any case, I manually overrode from the command line:
clawdock-exec node dist/index.js config set tools.exec.host gateway
clawdock-exec node dist/index.js config set tools.exec.ask off
clawdock-exec node dist/index.js config set tools.exec.security full
So my question:
1) Was that the right approach to "fix" the issue that the agent could not longer execute commands? Doctor --repair on the gateway was unhelpful
2) security audit --deep seems fine but is that the right config to allow the agent to run itself without huge security gaps?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
