/org/{org}/sandboximage/{name}. It is managed from the Console or the API; the cpln sandboximage command group covers it: create --name <n> [--base-image //image/<name>:<tag>] [--image-tag <tag>] [--type dev|agent] (an agent image needs --base-image), rebuild <ref...>, buildlog <ref> [-f] [--offset N], and get, delete, edit, update (--set accepts description, tags.<k>, spec.base.image, spec.tag, spec.type), patch, tag, clone, query, eventlog, audit, access-report, and permissions.
Sandbox image spec
The recipe has one tenant-controlled input: the base image to buildFROM. There is no runtime, package, or install-command surface, so no arbitrary build shell runs under your org.
What the sandbox layer adds
The build takes your base (or the standard Ubuntu base) and layers the same components the standard dev image carries:
Persistent install paths (
~/.npm-global, ~/.local) are on PATH so packages you install inside the sandbox survive on the home volume.
If your base already has a uid 1000 user, it is renamed to
devuser with its home moved to /home/devuser. Application code is not part of the image: clone repositories inside the running sandbox.How a sandbox image build runs
- Creating the object, or changing its recipe (
spec, or acpln/tag such ascpln/restartedAt), submits a build to the platform build service under the caller’s own token. The caller needs imagecreatein the org, the same right a registry push needs. Nothing holds the token past the call. - The built image lands in the org registry as an org image;
status.imageLinkpoints at it. - The build status is refreshed whenever the object is read.
- The object’s event log at
.../sandboximage/{name}/-eventlogrecords the build’s life: submission, queued, running, pushed or failed with the reason, and any failure to reach the build service. - The build output itself is at
.../sandboximage/{name}/-buildlog; page through it with-buildlog?offset=N. - Delete answers
202and leaves the built org image in place. - The org quota
sandboximagesPerOrgcaps how many sandbox images an org holds.
Sandbox image status
Sandbox image API examples
Create an image built on your own base:cpln sandboximage rebuild python-tools, or by setting a cpln/restartedAt tag:
Using a sandbox image on a sandbox
Set the built image as the dev container image of a dev sandbox. In the Console, the Image field of the sandbox form lists Your Sandbox Images next to Standard. Through the CLI, pass the sandbox image link and the CLI resolves it to the built reference:--type worker, an agent-type image, an image whose build is not ready or has failed (follow it with cpln sandboximage buildlog python-tools -f), and a gvc-scoped link; any other --image value passes through. Through the API, or as the alternative on the CLI, pass the registry reference from status.imageRef: