researchclaw-dedicated-container-not-inside-hermes

AutoResearchClaw MUST run in a dedicated container (researchclaw) on oracle-network, NOT installed inside the oracle-hermes container. AutoResearchClaw executes generated experiment code that requires sandboxing — running it inside Hermes would create both security risk and Python dependency conflicts. The dedicated container uses Docker-in-Docker or host Docker socket for its own experiment sandbox containers, matching the existing oracle-* topology pattern.

Related

• researchclaw-dedicated-container-oracle-network-topology
• autoresearchclaw-must-run-in-dedicated-container-for-sandbox
• autoresearchclaw-requires-dedicated-container-for-experiment
• researchclaw-must-run-in-dedicated-container-for-sandboxing
• autoresearchclaw-requires-dedicated-container-for-sandbox
• researchclaw-requires-docker-isolation-not-host-install
• hostinger-kvm8-is-shared-cpu-plan
• docker-iptables-bypasses-ufw-docker-user-chain-required