Terminal
Terminal/Skill
Builds and deploys Docker containers on Render from Dockerfiles or prebuilt images, covering multi-stage builds, registries, and caching.
By Render
Works with
npx skills add render-oss/skills --skill render-dockerRender uses BuildKit for Docker builds. All compute service types that support custom runtimes can use runtime: docker (build from a Dockerfile in the repo) or runtime: image (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under references/.
runtime: docker vs runtime: image in a BlueprintFor full Blueprint authoring, see render-blueprints. For end-to-end deploy flows, see render-deploy.
Before deploying a built or prebuilt image, read references/deployments.md for current trigger, lifecycle, health-check, and signal behavior.
runtime: docker: Render builds an image from your repo using dockerfilePath, dockerContext, and optional dockerCommand (overrides image CMD).runtime: image: Render pulls image.url; no repo-based image build. Set image.creds.fromRegistryCreds.name when the registry is private.| Field | Role |
|---|---|
dockerfilePath | Path to the Dockerfile (default ./Dockerfile) |
dockerContext | Build context directory (what is sent to the daemon) |
dockerCommand | Overrides the container CMD after the image is built |
image.url | Image reference for runtime: image (registry/repo:tag or digest) |
image.creds | Dashboard-stored credential reference for a private prebuilt image |
registryCredential | Dashboard-stored credential reference for private base images used by runtime: docker |
Example sketch (values illustrative):
services:
- type: web
name: api
runtime: docker
region: oregon
plan: starter
dockerfilePath: ./Dockerfile
dockerContext: .
dockerCommand: node server.js
envVars:
- key: PORT
value: 10000
For runtime: image, set image.url and, if needed, image.creds per Registry Configuration below.
Recommended for production. Use a builder stage for compilation and dependency installation, and a minimal runner stage that only copies artifacts and runtime files. Benefits:
See references/dockerfile-patterns.md for language-specific templates.
Critical: Never pass secrets via ARG. Build arguments are stored in image layers and can be recovered from the image history or intermediate layers.
RUN --mount=type=secret,...) rather than ARG.Treat anything sensitive as runtime or BuildKit secret mount, not as a build arg.
Private base images (for runtime: docker) or prebuilt images (runtime: image) need authentication:
runtime: docker, reference private base-image credentials with registryCredential.fromRegistryCreds.name.runtime: image, reference private prebuilt-image credentials with image.creds.fromRegistryCreds.name.Supports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: references/registry-setup.md.
Prebuilt-image services do not automatically deploy when a mutable registry tag moves. After publishing a new image, trigger a manual deploy through the Dashboard or a supported API or deploy-hook flow. Prefer immutable tags or digests so each deploy identifies an explicit artifact; follow references/deployments.md for the complete trigger and verification workflow.
references/optimization-guide.md).latest can resolve to stale cached images. Prefer immutable references: digest (repo/image@sha256:...) or version pins (v1.2.3).0.0.0.0:$PORT (Render sets PORT).references/deployments.md./etc/secrets/ — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image..dockerignore and Start Commands.dockerignore that excludes node_modules, .git, .env, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: references/optimization-guide.md./bin/sh -c 'set -e; ./migrate && exec node server.js' (prefer exec so your app receives signals for graceful shutdown).| Document | Contents |
|---|---|
references/dockerfile-patterns.md | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) |
references/registry-setup.md | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring |
references/optimization-guide.md | Layer order, .dockerignore, BuildKit cache mounts, debugging |
references/deployments.md | Deploy triggers, lifecycle, health checks, shutdown, and verification |
render.yaml schema, wiring, and validationWhenever this skill directs you to consult current Render documentation:
curl. Do not substitute web-search summaries for the document.When a task requires multiple references, apply this workflow to each one and distinguish the documents you verified from those that remain unavailable.