researchclaw-dedicated-container-isolation-requirement

AutoResearchClaw must run in a dedicated container (not inside oracle-hermes) because it executes generated experiment code during the pipeline — sandboxed execution is a hard requirement. The container joins oracle-network alongside oracle-hermes, oracle-mirofish, and oracle-graphiti-mcp. Docker-in-Docker or host Docker socket binding is needed for AutoResearchClaw’s own experiment sandbox containers.

Related

• autoresearchclaw-requires-dedicated-container-for-sandbox
• researchclaw-must-run-in-dedicated-container-for-experiment
• researchclaw-requires-dedicated-container-with-docker-socket
• researchclaw-dedicated-container-oracle-network-deployment
• autoresearchclaw-container-topology-oracle-network
• hostinger-kvm8-is-shared-cpu-plan
• docker-iptables-bypasses-ufw-docker-user-chain-required
• docker-iptables-bypasses-ufw-requires-docker-user-chain
• hostinger-cloud-firewall-is-upstream-gate-not-ufw
• hostinger-cloud-firewall-is-upstream-gate-docker-bindings-no