Sign inSign up

docker/sbx-kit-nanoclaw-mixin

Verified Publisher

By Docker, Inc.

•Updated 9 days ago

NanoClaw as a mixin -- the host process and its checkout in an overlay, with the Docker Hub, OneC...

Sandbox Kit
0

92

docker/sbx-kit-nanoclaw-mixin repository overview

Digest

sha256:4dec59081491…

Size

76 MB

Schema

v3

Pushed

9 days ago

Specificationspec.yaml

MIXIN

NanoClaw as a mixin -- the host process and its checkout in an overlay, with the Docker Hub, OneCLI, Claude and chat-channel egress and the published webhook and OneCLI ports. Layer it onto a base that already carries a Node runtime and run `nanoclaw-start`.


Providesnanoclaw

CapabilitiesExpand a row to see its full configuration. See the full spec for the complete descriptor.
TypeRequiredDescription
com.docker.sandbox/network-policy@1Required—
com.docker.sandbox/port@1Required—
com.docker.sandbox/port@1Required—
com.docker.sandbox/port@1Required—
com.docker.sandbox/agent-context@1Required—

Requiresdeb/docker-ce

Apply this mixin to a sandbox

sbx run <agent> --kit docker/sbx-kit-nanoclaw-mixin:latest

Make sure you have docker sbx installed

Run the following command to install sbx on your machine.

macOS
brew install docker/tap/sbx
Windows
winget install Docker.sbx
Learn more about docker sbx⁠

Note

Experimental: Sandbox Kit v3

This kit uses the experimental Sandbox Kit specification⁠, specifically v3⁠. The format and runtime behavior may change before v3 is stable.

⁠nanoclaw-mixin

NanoClaw⁠ as a mixin — the same agent as the nanoclaw⁠ workload kit, packaged as an overlay you layer onto an existing base instead of running as the sandbox's own image.

Read this first. NanoClaw is distributed as a prebuilt third-party image, not as an install this repo drives. An overlay is a delta, so this mixin carries the NanoClaw host launcher and its checkout — and not the Node runtime, OneCLI and Postgres clients, and system packages that image installs around them. Compose it only onto a base that already carries an equivalent runtime. If you want a sandbox that just works, use the workload kit.

⁠Usage

sbx run --kit ./nanoclaw-mixin/ <base-workload>

Or from a git URL targeting this repository:

sbx run --kit "git+https://github.com/docker/sbx-kits-contrib.git#dir=nanoclaw-mixin" <base-workload>

The base workload keeps its own launch command, so nothing starts NanoClaw for you:

/usr/local/bin/nanoclaw-start

⁠What it carries

  • /usr/local/bin/nanoclaw-start and /home/agent/nanoclaw, copied out of the published NanoClaw image.
  • The Docker Hub, OneCLI, Claude, GitHub, package and chat-channel egress the workload declares.
  • The webhook (3000) and OneCLI dashboard/gateway (10254, 10255) ports.
  • NanoClaw's environment variables, as a profile.d export — a mixin's image config does not become the composed image's.

⁠What it deliberately leaves to the base workload

  • The launch command. A mixin does not set an entrypoint.
  • The runtime NanoClaw needs. See the note above; v3 has no way to state this requirement, because requires: names kit capabilities and no base workload provides one for its interpreter.
  • The context-file profile. filename: is workload-only; this kit contributes a body through contentFile.

This week's pulls

Pulls:

56

Last week