feat(runtime): execute docker environment recipes#1676
Merged
Conversation
Bead: av-noh3.2.4
Deploying agentv with
|
| Latest commit: |
4ea20c5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2ffca2c9.agentv.pages.dev |
| Branch Preview URL: | https://environment-docker-runtime.agentv.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docker environment recipes now prepare a local Docker image/context and run generic CLI targets inside that environment with
environment.workdiras the command cwd. The environment recipe remains separate from target/provider selection: Docker setup builds or pulls the image, produces a sandbox runtime for compatible CLI targets, and unsupported provider combinations return structured sandbox-infra results instead of falling back to host execution.Implementation Notes
type: dockerrecipes withimage,context,dockerfile,workdir,env,secrets,mounts,resources.cpus,resources.memory, andsetup.command/setup.args/setup.env.{PROMPT_FILE}and{OUTPUT_FILE}paths remain available across the host/managed Docker boundary.Validation
bunx biome check packages/core/src/evaluation/environment/docker.ts packages/core/src/evaluation/workspace/setup.ts packages/core/src/evaluation/providers/sandbox-runner.ts packages/core/src/evaluation/orchestrator.ts packages/core/test/evaluation/environment/docker.test.ts packages/core/test/evaluation/orchestrator.test.tsbun test packages/core/test/evaluation/environment/docker.test.ts packages/core/test/evaluation/orchestrator.test.ts packages/core/test/evaluation/providers/cli.test.ts packages/core/test/evaluation/providers/sandbox-runtime.test.tsbun run typecheckgit diff --checkDogfood Evidence
Controlled Docker CLI target:
bun apps/cli/src/cli.ts eval /tmp/agentv-docker-env-dogfood/docker-env.eval.yaml --targets /tmp/agentv-docker-env-dogfood/targets.yaml --target docker-cli --workers 12026-07-05T10-52-06-267Z.agentv/results/2026-07-05T10-52-06-267Zcli, runtimesandbox, command cwd/app.Live LLM grader with Docker CLI target:
bun apps/cli/src/cli.ts eval /tmp/agentv-docker-env-dogfood/docker-env-live-grader.eval.yaml --targets /tmp/agentv-docker-env-dogfood/targets-live-grader.yaml --target docker-cli-live-graded --workers 12026-07-05T10-53-51-519Z.agentv/results/2026-07-05T10-53-51-519Zcli; grader target OpenAI-compatible provider via GitHub Models.sandbox, command cwd/app, exit code 0.Private evidence was published to
agentv-private:evidence/av-noh3-2-4-docker-environment-runtimeat commitbd0f659.Post-Deploy Monitoring & Validation
After merge, validate the first environment docs/example PR against this behavior with one Docker recipe that uses an image and one that builds from context/dockerfile. Watch CI failures around sandbox runtime tests and CLI output-file handling, because those paths depend on the host temp-dir mount being available inside Docker.
Related
Bead: av-noh3.2.4