Docker's published Claude Code Kit is refused: sbx@1 not provided #1873

Closed
opened 2026-11-12 09:43:24 +00:00 by sam · 1 comment
Owner

Problem

docker.io/docker/sbx-kit-claude (v2.1.314, built with sandbox-kit 3.0.0-m.11) declares com.docker.sandbox/sbx@1 as a required capability. kit.SelectCapability refuses any type outside supported, so resolution fails with capabilities[0]: required capability selection rejected ... not provided by archie. Reproduced on main with a throwaway resolve of that digest through kit.SelectCapability and kit.FromResolved. The PRD's "Published Kits run unmodified" does not hold, and no Kit run can be tried with Docker's own Claude Code Kit.

What sbx@1 asks of the runtime

From the spec page for sbx@1 in sandbox-kit-spec m.12:

  1. The image entrypoint is not PID 1. Archie already does this (the worker is PID 1).
  2. Agent, hooks and file writes run as the image config's user, resolved from /etc/passwd. Archie uses the image User; check it resolves uid, gid and home rather than assuming 1000.
  3. The agent is launched under bash so BASH_ENV is sourced. Archie execs Entrypoint + Cmd directly (kit.Assemble, harnessArgv). The Claude Kit sets BASH_ENV=/etc/sandbox-persistent.sh.
  4. The workspace sits at the image's absolute WorkingDir. Archie mounts it at the fixed kit.WorkspaceDir (/archie/workspace). The Claude Kit's is /home/agent/workspace.

Done when

  • sbx@1 is in supported, with items 2 to 4 implemented.
  • The Claude Code Kit at a pinned digest resolves and runs a stage end to end.
  • Test for the workspace path and the bash launch (workflow step contract).

Related: #1865.

## Problem `docker.io/docker/sbx-kit-claude` (v2.1.314, built with sandbox-kit 3.0.0-m.11) declares `com.docker.sandbox/sbx@1` as a required capability. `kit.SelectCapability` refuses any type outside `supported`, so resolution fails with `capabilities[0]: required capability selection rejected ... not provided by archie`. Reproduced on main with a throwaway resolve of that digest through `kit.SelectCapability` and `kit.FromResolved`. The PRD's "Published Kits run unmodified" does not hold, and no Kit run can be tried with Docker's own Claude Code Kit. ## What sbx@1 asks of the runtime From the spec page for `sbx@1` in sandbox-kit-spec m.12: 1. The image entrypoint is not PID 1. Archie already does this (the worker is PID 1). 2. Agent, hooks and file writes run as the image config's user, resolved from `/etc/passwd`. Archie uses the image `User`; check it resolves uid, gid and home rather than assuming 1000. 3. The agent is launched under `bash` so `BASH_ENV` is sourced. Archie execs `Entrypoint + Cmd` directly (`kit.Assemble`, `harnessArgv`). The Claude Kit sets `BASH_ENV=/etc/sandbox-persistent.sh`. 4. The workspace sits at the image's absolute `WorkingDir`. Archie mounts it at the fixed `kit.WorkspaceDir` (`/archie/workspace`). The Claude Kit's is `/home/agent/workspace`. ## Done when - `sbx@1` is in `supported`, with items 2 to 4 implemented. - The Claude Code Kit at a pinned digest resolves and runs a stage end to end. - Test for the workspace path and the bash launch (workflow step contract). Related: #1865.
Author
Owner

Superseded by #1877: Kit support is being deleted, so sbx@1 won't be implemented.


Generated by Claude Code

Superseded by #1877: Kit support is being deleted, so sbx@1 won't be implemented. --- _Generated by [Claude Code](https://claude.ai/code)_
sam closed this issue 2026-11-12 09:48:59 +00:00
sam added the highbug labels 2026-11-12 15:51:30 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1873