What are Prime Images?
Prime Images lets you push custom Docker images to Prime’s registry and use them in sandboxes. Builds happen in the cloud, so you don’t need Docker running locally.Push an Image
--source-image to transfer a public image from Docker Hub, GHCR, Quay, public ECR, registry.k8s.io, or MCR without building from a Dockerfile.
When the push completes, the CLI prints the full image reference to use when creating a sandbox. Prime Image references always start with prime/. By default this uses your unique slug — your username for personal images, or the team slug when you’re in a team context:
prime/<userId>/myapp:v1.0.0 or prime/team-<teamId>/myapp:v1.0.0. Run prime images list to see the exact reference for each image.
Check Build Status
- Ready – Build succeeded, image is usable
- Building – Build in progress
- Pending – Queued for build
- Failed – Build failed (check your Dockerfile)
Use Your Image
Once the status shows Ready, create a sandbox with it:VM Images
VM sandboxes are the default runtime, and they boot a VM image rather than a container image. You still define images the normal way — build from a Dockerfile withprime images push, and accounts with VM sandboxes enabled get a VM image automatically.
The first time a given image is launched, Prime converts it into a VM image. The sandbox sits in PENDING while that runs, which can take a few minutes; later sandboxes from the same image start normally.
Private-registry credentials (--registry-credentials-id) are coming soon to VM sandboxes. Use --container for now.
Pre-build a VM image
Convert ahead of time so the first launch is fast:linux/amd64, and your account needs VM sandboxes enabled.
Publish or Unpublish an Image
Images are private by default. Publishing an image lets other authenticated Prime users use it in sandboxes with theprime/ reference shown by prime images list.