docker
/docker
Execute research code inside isolated Docker containers for safe replication, experiments, and benchmarks. Use when the user selects Docker as the execution environment or asks to run code safely, in isolation, or in a sandbox.
- Author
- companion-inc ↗
- Repository
- feynman ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Execute research code inside isolated Docker containers for safe replication, experiments, and benchmarks. Use when the user selects Docker as the execution environment or asks to run code safely, in isolation, or in a sandbox.
Original author description
Execute research code inside isolated Docker containers for safe replication, experiments, and benchmarks. Use when the user selects Docker as the execution environment or asks to run code safely, in isolation, or in a sandbox.
How it works
- When to use
- How it works
- Running commands in a container
- Choosing the base image
- Persistent containers
- Notes
SKILL.md preview
--- name: docker description: Execute research code inside isolated Docker containers for safe replication, experiments, and benchmarks. Use when the user selects Docker as the execution environment or asks to run code safely, in isolation, or in a sandbox. allowed-tools: Bash(docker:*) --- # Docker Sandbox Run research code inside Docker containers while Feynman stays on the host. The container gets the project files, runs the commands, and results sync back. ## When to use - User selects "Docker Sandbox" as the execution environment in `/replicate` or `/autoresearch` - Running untrusted code from a paper's repository - Experiments that install packages or modify system state - Any time the user asks to run research code safely or isolated for a Feynman workflow ## How it works 1. Build or pull an appropriate base image for the research code 2. Mount the project directory into the container 3. Run experiment commands inside the container 4. Results write back to the mounted directory ## Running commands in a container For Python research code (most common): ```bash docker run --rm -v "$(pwd)":/workspace -w /workspace python:3.11 bash -c " pip install -r requirements.txt && python train.py " ``` For projects with a Dockerfile: ```bash docker build -t feynman-experiment . docker run --rm -v "$(pwd)/results":/workspace/results feynman-experiment ``` For GPU workloads: ```bash docker run --rm --gpus all -v "$(pwd)":/workspace -w /workspace pytorch/pytorch:latest bash -c " pip install -r requirements.txt && python train.py " ``` ## Choosing the base image | Research type | Base image | | --- | --- | | Python ML/DL | `pytorch/pytorch:latest` or `tensorflow/tensorflow:latest-gpu` | | Python general | `python:3.11` | | Node.js | `node:20` | | R / statistics | `rocker/r-ver:4` | | Julia | `julia:1.10` | | Multi-language | `ubuntu:24.04` with manual installs | ## Persistent containers For iterative experiments (like `/autoresearch`), create a named container instead of `--rm`. Choose a descriptive name based on the experiment: ```bash docker create --name <name> -v "$(pwd)":/workspace -w /workspace python:3.11 tail -f /dev/null docker start <name> docker exec <name> bash -c "pip install -r requirements.txt" docker exec <name> bash -c "python train.py" ``` This preserves installed packages across iterations. Clean up with: ```bash docker stop <name> && docker rm <name> ``` ## Notes - The mounted workspace syncs results back to the host automatically - Containers are network-enabled by default — add `--network none` for full isolation - For GPU access, Docker must be configured with the NVIDIA Container Toolkit
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · companion-inc/feynman | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| atomicbot-ai/atomic-agent | 100 | MIT |
| aleks-spv/sysaiadm_station | 100 | AGPL-3.0 |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
| greedychipmunk/agent-skills | 100 | MIT |
| poppyszn/dev-pops-skills | 100 | MIT |
| G1Joshi/Agent-Skills | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 207661974df2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100verifying-agent-generated-code-in-isolated-runtimes
Use this skill when execute and verify agent-generated scripts inside ephemeral, isolated sandbox containers. - 100sindoq
Execute code in sandboxed environments using Docker, Podman, Wasmer, gVisor, Firecracker, Kubernetes, or cloud providers. Use when the user needs to safely run untrusted code, build AI code execution pipelines, or set up isolated sandbox environments. - 100agent-sandbox
Run AI agent code safely in isolated sandboxes with resource limits, audit trails, and kill switches. Use when someone asks to "sandbox my agent", "run agent code safely", "add guardrails to AI agent", "isolate agent execution", "audit agent actions", "prevent agent from… - 100abx-sandbox-docker
Run Docker inside an AgentBox sandbox — building images, docker compose, and reaching an internal registry from in there. Use when a workload needs a container runtime of its own, when `docker` is not found inside a sandbox, or when someone asks about Docker-in-Docker isolation.… - 100docker-agent-run
Use this skill when running a Docker Agent with `docker agent run`, choosing a safety/approval mode, using the `--sandbox` isolation flag, setting up aliases, or troubleshooting a run (missing credentials, worktrees). Even if the user just says they want to "run my agent", "make… - 100orbit
Run experiments (training, evaluation, sweeps, any GPU job) in isolated Docker containers with Orbit, and read back their logs, metrics and outputs. Use whenever you would otherwise run a long or GPU job directly on the host, launch several seeds or hyperparameter settings, or…