skills/depot-container-builds/SKILL.md
Configures and runs Depot remote container builds using `depot build` and `depot bake`. Use when building Docker images, creating Dockerfiles with Depot, pushing images to registries, building multi-platform/multi-arch images (linux/amd64, linux/arm64), debugging container build failures, optimizing Dockerfile layer caching, using docker-bake.hcl or docker-compose builds, or migrating from `docker build` / `docker buildx build` to Depot. Also use when the user mentions depot build, depot bake, container builds, image builds, or asks about Depot's build cache, build parallelism, or ephemeral registry.
npx skillsauth add depot/skills depot-container-buildsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Depot runs Docker image builds on remote high-performance builders (16 CPU, 32 GB RAM, NVMe SSD cache). depot build is a drop-in replacement for docker build / docker buildx build. depot bake replaces docker buildx bake.
Container build commands target a specific project, not an organization. If expected projects aren't visible or a build unexpectedly prompts to select a project, the current default org may be wrong:
depot org show # Current org ID
depot org list # Orgs the user belongs to
depot org switch <org-id> # Optional: set default org
--load to download to local Docker, --push to push to a registry, --save to store in Depot's ephemeral registrydepot build — Essential Patterns# Build remotely (image stays in remote cache)
depot build -t repo/image:tag .
# Build + download to local Docker daemon
depot build -t repo/image:tag . --load
# Build + push directly to registry (fast — doesn't route through local network)
depot build -t repo/image:tag . --push
# Multi-platform build (native CPUs, no emulation)
depot build --platform linux/amd64,linux/arm64 -t repo/image:tag . --push
# Save to Depot ephemeral registry (default 7-day retention)
depot build --save .
depot build --save --save-tag my-tag .
# Suppress provenance metadata (fixes "unknown/unknown" platform in registries)
depot build -t repo/image:tag --push --provenance=false .
# Lint Dockerfile before building
depot build -t repo/image:tag . --lint
# Build with secrets
depot build --secret id=mysecret,src=./secret.txt -t repo/image:tag .
# Build with SSH forwarding
depot build --ssh default -t repo/image:tag .
# Specify a Depot project explicitly
depot build --project <project-id> -t repo/image:tag .
|Flag |Description |
|------------------|-------------------------------------------------------------------|
|--load |Download image to local Docker daemon |
|--push |Push to registry |
|--save |Save to Depot ephemeral registry |
|--save-tag |Custom tag for Depot Registry |
|--platform |Target platforms (linux/amd64, linux/arm64, or both) |
|--build-platform|Force build to run on specific arch (dynamic default) |
|--project |Depot project ID |
|--token |Depot API token |
|--lint |Lint Dockerfile before build |
|--provenance |Control provenance attestation (set false to fix unknown/unknown)|
|--no-cache |Disable cache for this build |
|-f / --file |Path to Dockerfile |
|-t / --tag |Image name and tag |
|--target |Build specific stage |
|--build-arg |Set build-time variables |
|--secret |Expose secrets (id=name[,src=path]) |
|--ssh |Expose SSH agent |
|--output / -o |Custom output (type=local,dest=path) |
depot bake — Multi-Image BuildsDrop-in replacement for docker buildx bake. Builds multiple images in parallel.
depot bake # Default file lookup
depot bake -f docker-bake.hcl # Specific HCL file
depot bake -f docker-compose.yml --load # Build compose services + load locally
depot bake --save --save-tag myrepo/app:v1 # Save to Depot Registry
depot bake --print # Print resolved config without building
Default file lookup order: compose.yaml → compose.yml → docker-compose.yml → docker-compose.yaml → docker-bake.json → docker-bake.override.json → docker-bake.hcl → docker-bake.override.hcl
variable "TAG" {
default = "latest"
}
group "default" {
targets = ["app", "worker"]
}
target "app" {
dockerfile = "Dockerfile"
platforms = ["linux/amd64", "linux/arm64"]
tags = ["myrepo/app:${TAG}"]
args = { NODE_VERSION = "20" }
}
target "worker" {
dockerfile = "Dockerfile.worker"
tags = ["myrepo/worker:${TAG}"]
contexts = { app = "target:app" } # Share base between targets
}
Override variables: TAG=v2.0 depot bake
services:
api:
build:
dockerfile: ./Dockerfile.api
x-depot:
project-id: abc123
web:
build:
dockerfile: ./Dockerfile.web
x-depot:
project-id: def456
# Preferred: build all services in parallel, then load
depot bake -f docker-compose.yml --load
docker compose up
# Alternative: zero code change (less efficient, each service = separate build)
depot configure-docker
docker compose build
# docker build → depot build (same flags, one-line swap)
depot build -t my-image .
# docker buildx bake → depot bake
depot bake -f docker-bake.hcl
# Zero code change via Docker plugin
depot configure-docker
docker build . # Routes through Depot (look for [depot] prefix in logs)
When migrating, remove these flags — Depot handles caching automatically:
--cache-from type=gha — causes "services aren't available" errors--cache-to type=gha — same issue|Mistake |Fix |
|------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
|Using --cache-from type=gha or --cache-to type=gha|Remove them. Depot caches automatically on NVMe SSDs. |
|Multi-platform image shows unknown/unknown platform |Add --provenance=false |
|Expecting image locally after depot build |Add --load to download, or --push to push to registry |
|.git directory missing in build context |Add --build-arg BUILDKIT_CONTEXT_KEEP_GIT_DIR=1 |
|Build hangs or "failed to mount" errors |Reset cache in project settings or via depot cache reset |
|"401 Unauthorized" pulling base images |Docker Hub rate limit — authenticate with docker login or use public.ecr.aws/docker/library/ mirror|
|"Keep alive ping failed" / OOM |Scale up builder size in project settings or enable autoscaling |
|Size |CPUs|RAM |Per-Minute|Plans | |-----------|----|------|----------|--------| |Default |16 |32 GB |$0.004 |All | |Large |32 |64 GB |$0.008 |Startup+| |Extra Large|64 |128 GB|$0.016 |Startup+|
Billed per-second. Bake counts as one build regardless of target count.
# Save image to Depot Registry
depot build --save -t myapp .
# Pull a saved image
depot pull --project <id> <build-id>
# Push saved image to another registry
depot push --project <id> -t registry/image:tag <build-id>
# Docker auth for Depot Registry
docker login registry.depot.dev -u x-token -p <depot-token>
# Registry URL: registry.depot.dev/<project-id>:<tag>
# estargz (lazy-pulling for faster container startup)
depot build --output "type=image,name=repo/image:tag,push=true,compression=estargz,oci-mediatypes=true,force-compression=true" .
# zstd compression (faster Fargate/K8s startup)
depot build --output type=image,name=repo/image:tag,oci-mediatypes=true,compression=zstd,compression-level=3,force-compression=true,push=true .
tools
Configures Depot-managed GitHub Actions runners as a drop-in replacement for GitHub-hosted runners. Use when setting up or migrating GitHub Actions workflows to use Depot runners, choosing runner sizes (CPU/RAM), configuring runs-on labels, setting up ARM or Windows or macOS runners, troubleshooting GitHub Actions runner issues, configuring egress filtering, using Depot Cache with GitHub Actions, or running Dagger/Dependabot on Depot runners. Also use when the user mentions depot-ubuntu, depot-windows, depot-macos runner labels, or asks about faster/cheaper GitHub Actions runners.
tools
Handles Depot CLI installation, authentication, login, project setup, organization management, and API access. Use when installing the Depot CLI, logging in with `depot login`, creating or managing Depot projects, configuring API tokens or OIDC trust relationships, setting up depot.json, managing organizations, resetting build caches, or using the Depot API/SDKs. Also use when the user asks about Depot authentication methods, token types, environment variables, or general Depot platform setup that isn't specific to container builds, GitHub Actions runners, or Depot CI.
development
Configures and manages Depot CI, a drop-in replacement for GitHub Actions that runs workflows entirely within Depot. Use when migrating GitHub Actions workflows to Depot CI, running `depot ci migrate`, managing Depot CI secrets and variables, running workflows with `depot ci run`, debugging Depot CI runs with `depot ci run list`, `depot ci status`, `depot ci logs`, or `depot ci ssh`, checking workflow compatibility, or understanding Depot CI capabilities. Also use when the user mentions .depot/ directory, depot ci commands, or asks about running GitHub Actions workflows on Depot's infrastructure without GitHub-hosted runners.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.