Registry

Push Docker images to your workspace's private container registry using the edge CLI.

The edge registry commands let you push Docker images to your workspace's private registry at sdcr.io directly from the terminal — no manual docker login required.

The CLI fetches short-lived push credentials from the API automatically and handles tagging and pushing via the Docker SDK.

All registry commands require a workspace (-w). A running Docker daemon is also required for push operations.

push

Tag a local image and push it to your workspace registry.

edge registry push <image>:<tag> -w <workspace>

Arguments

Argument	Description
`image:tag`	Local image name and tag to push. If omitted in an interactive terminal, you will be prompted.

Examples

# Push a specific image and tag
edge registry push myapp:1.0 -w my-workspace

# Push using the active workspace from context
edge registry push myapp:latest

Example output

→ Registry: my-registry (sdcr.io/my-registry)
→ Pushing to sdcr.io/my-registry/myapp:1.0
✓ Successfully pushed sdcr.io/my-registry/myapp:1.0

JSON output

edge registry push myapp:1.0 -w my-workspace --json

{
  "image": "sdcr.io/my-registry/myapp:1.0"
}

Full workflow example

# 1. Build your image locally
docker build -t myapp:1.0 .

# 2. Push to your workspace registry
edge registry push myapp:1.0 -w my-workspace

# 3. Create a service that uses the pushed image
edge service create \
  --name myapp \
  --type docker \
  --image sdcr.io/my-registry/myapp \
  --tag 1.0 \
  -w my-workspace -p my-project -e production

# 4. Deploy it
edge deploy up myapp -w my-workspace -p my-project -e production

Errors

Message	Cause	Fix
`no registry configured for this workspace`	The workspace has no registry namespace	Create one in Project Settings → Registry
`tagging image: Error response from daemon: No such image`	The local image does not exist	Run `docker build` or `docker pull` first
`not authenticated`	No token found	Run `edge auth login` or set `CLOUD_TOKEN`