> ## Documentation Index
> Fetch the complete documentation index at: https://docs.primeintellect.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Prime Images

> Build and manage custom Docker images for sandboxes

## 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

```bash theme={null}
# Basic push (uses ./Dockerfile in current directory)
prime images push myapp:v1.0.0

# Make the image public when the build completes
prime images push myapp:v1.0.0 --public

# Specify a different Dockerfile
prime images push myapp:v1.0.0 --dockerfile custom.Dockerfile

# Use a different build context
prime images push myapp:v1.0.0 --context ./app

# Copy an existing public image into Prime's registry
prime images push --source-image ubuntu:22.04

# Copy and rename the destination tag
prime images push myubuntu:22.04 --source-image ubuntu:22.04
```

The CLI packages your build context, uploads it, and kicks off a remote build. You'll get a build ID to track progress.

Use `--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:

```text theme={null}
prime/<your-username>/myapp:v1.0.0      # personal
prime/<team-slug>/myapp:v1.0.0          # team
```

If you haven't set a username (or your team has no slug yet), the reference falls back to the id form — `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

```bash theme={null}
# See all your images and their build status
prime images list
```

Status meanings:

* **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:

```bash theme={null}
# Personal image
prime sandbox create prime/<your-username>/myapp:v1.0.0 --cpu-cores 2 --memory-gb 4

# Team image
prime sandbox create prime/<team-slug>/myapp:v1.0.0 --cpu-cores 2 --memory-gb 4
```

## Publish or Unpublish an Image

Images are private by default. Publishing an image lets other authenticated Prime users use it in sandboxes with the `prime/` reference shown by `prime images list`.

```bash theme={null}
prime images publish myapp:v1.0.0
prime images unpublish myapp:v1.0.0
```

## Delete an Image

```bash theme={null}
prime images delete myapp:v1.0.0

# Skip confirmation
prime images delete myapp:v1.0.0 --yes
```