Priya RamanandPaperclip
fb0ef89624
Copy the repository .cargo directory into the Daytona runner Docker build stage, so the production cargo build picks up the raised retry count and transfer timeout instead of the cargo defaults. Add .cargo to the audited Daytona image input paths, so a future change to that file invalidates the cached image. Make Arm B of the network stall differential harness unset CARGO_NET_RETRY and CARGO_HTTP_TIMEOUT before it runs cargo fetch, so the harness tests the repository config instead of a value the caller happens to have exported. Correct the .cargo/config.toml comment: the retry count rises from Cargo's default of 3 to 5, which is two more retries, not one. Co-authored-by: Paperclip <noreply@paperclip.ing>
Paperclip Daytona runner image
This image is the Paperclip Cloud fleet sandbox image plus a source-built
paperclip-runnerd and immutable provider pack. The pack contains Node 24.11,
OpenCode 1.18.17, the compiled OpenCode proxy, ACPX 0.13.1 sidecar, qualified ACP
agents, and the production lockfile. Its manifest digests each executable bridge
and binds the pack to the runner source revision, avoiding artifact upload and
npm installation on every fresh lease.
The fleet pins are intentionally copied from
paperclip-cloud/fleet-sandbox-image/Dockerfile.
Update both definitions together until the fleet base is published as a stable
image that this Dockerfile can extend directly.
Build and verify
The fleet image is currently amd64-only because the pinned Cursor and GitHub CLI checksums cover amd64.
content_id="$(pnpm --silent test:e2e:runner:image-id)"
docker buildx build \
--platform linux/amd64 \
--build-arg PAPERCLIP_RUNNER_CONTENT_ID="${content_id}" \
--build-arg PAPERCLIP_RUNNER_SOURCE_REVISION="$(git rev-parse HEAD)" \
--tag "paperclip-daytona-runner:e2e-content-${content_id}" \
--load \
--file docker/daytona-runner/Dockerfile \
.
docker run --rm --platform linux/amd64 \
--entrypoint paperclip-runnerd \
"paperclip-daytona-runner:e2e-content-${content_id}" \
--build-metadata
The metadata must advertise dial_ws_loopback, dial_wss, and listen_ws.
The explicit entrypoint is needed only for this local probe because Daytona's
base image uses its own long-running sandbox entrypoint.
test:e2e:runner:image-id hashes the audited Docker build dependency closure,
target platform, the immutable Dockerfile syntax-frontend digest, and every
immutable FROM reference. It fails before the paid workflow can build when
the frontend or a base is not pinned to a sha256 digest. When updating the
syntax version, resolve and review its registry digest and update both values in
the first Dockerfile line. Git commits that do not change those inputs reuse the
same content tag.
PAPERCLIP_RUNNER_SOURCE_REVISION remains the full Git SHA that built the first
published copy and is retained as provenance rather than cache identity.
Use in Paperclip
Publish the image to a registry Daytona can pull, or use the environment
editor's Configure image flow to produce a Daytona snapshot. Set the
environment image to that immutable tag or snapshot. Paperclip probes the
sandbox user's PATH for paperclip-runnerd and codex and checks
/opt/paperclip-runner/provider-pack for OpenCode and ACPX. It uses the pack
only when its complete manifest matches the controller's build-owned pack;
otherwise it stages the pack configured by
PAPERCLIP_RUNNER_REMOTE_PROVIDER_PACK_PATH. Remote OpenCode and ACPX never
fall back to host-local processes.
Do not promote paperclip-runner-e2e-20260826-v2 for OpenCode or ACPX. Build a
new immutable image or snapshot from a clean committed revision and pass that
full Git SHA as PAPERCLIP_RUNNER_SOURCE_REVISION.
Do not bake provider credentials, Paperclip bootstrap tickets, or Daytona preview tokens into this image. They remain per-run secret material.