Push a sandbox image
Imports a sandbox image or starts an image build.
image to import a registry image asynchronously. Without image, the
response provides an upload URL for a ZIP archive containing a Dockerfile and
its build context. Processing starts after upload.
Reusing name adds a version to the repository. The service assigns its tag;
the request doesn’t accept a tag name. This operation doesn’t create a sandbox.
Poll Get a sandbox image
for build status, then list its tags.
After a repeat push, the repository can briefly report the previous build’s
BUILT or FAILED status. Observe the new build’s processing before interpreting
a terminal status. Confirm a new tag is available before selecting that version.
For the source archive and registry procedures, see
Create a custom image.Authorizations
Headers
Optional team ID. Must match the team_id query parameter when both are supplied. If neither selector is supplied, defaults to the caller's only accessible team. Callers with multiple accessible teams must select a team. Requests without access to any team are forbidden.
1Query Parameters
Body
Push a sandbox image from a source archive or an existing registry image.
Scratch disk in megabytes attached to the temporary build environment for intermediate layers. Set it for large images that run out of space while building or importing. 0 builds in memory, which is the default. Teams with HIPAA compliance enabled accept only 0.
0 <= x <= 13107232768
Response
Request accepted.
Accepted image push. Acceptance does not imply readiness; poll GET /sandboxes/images/{image_name} until status is BUILT or FAILED.
Temporary signed URL for uploading the source ZIP archive with HTTP PUT. Present only when no source image was supplied. The uploaded ZIP archive must not exceed 5 GB. Uploading starts asynchronous processing. This storage upload is separate from the API endpoints.
"https://uploads.b10.run/images/base-image/20260916212658/source.zip?expires=2026-09-16T22%3A26%3A58Z&signature=demo-not-a-valid-upload-signature"
Headers the source archive upload must send, in addition to Content-Type, with exactly these names and values. Present only with upload_url, when memory or volume was set. upload_url is signed for these headers, so storage rejects an upload that omits or changes them. Treat names and values as opaque.