researchclaw-requires-dedicated-container-not-hermes-install
AutoResearchClaw executes generated experiment code during its 23-stage pipeline, which MUST be sandboxed. Installing it inside the existing oracle-hermes container couples dependency versions, risks conflicts, and eliminates experiment isolation. The correct deployment is a dedicated researchclaw container on oracle-network, using Docker-in-Docker or host Docker socket for its inner experiment sandbox containers.
Related
- autoresearchclaw-requires-dedicated-container-for-sandbox
- autoresearchclaw-requires-dedicated-container-sandbox
- autoresearchclaw-requires-dedicated-container-for-experiment
- researchclaw-container-isolation-required-for-experiment-cod
- autoresearchclaw-dedicated-container-not-inside-hermes
- researchclaw-dedicated-container-for-experiment-sandboxing
- autoresearchclaw-must-run-in-dedicated-container-for-sandbox
- autoresearchclaw-experiment-sandbox-requires-docker-isolatio
- researchclaw-requires-docker-isolation-not-host-install
- npm-force-install-can-overwrite-system-binaries
- floating-latest-docker-tags-resolve-differently-mid-upgrade