Dockerfile deployments

Git-based Dockerfile Apps build an immutable image per commit with health-gated activation.

Who can use this page? Site managers deploying Dockerfile App sites.

Repository contract

1. Dockerfile path relative to application root (normally Dockerfile)
2. Internal port the app listens on (not published on the host)
3. Health path — non-5xx without authentication
4. Frontend/config values as non-sensitive env vars with Available at build time; Dockerfile must declare matching ARGs
5. Secrets Sensitive and runtime-only
6. Optional single Persistent Data Path (e.g. /app/uploads)

Example

Application root: .
Dockerfile: Dockerfile
Internal port: 80
Health check: /api/health/ready
Persistent data path: /app/uploads   # optional

Limits

• Memory limit, PID limit, restart policy, private network, no-new-privileges
• No privileged mode, host network, arbitrary mounts, or Docker socket

Images and rollback

• Each successful commit → immutable local image
• Failed health check → previous image restored
• Old images pruned with source release retention
• Activation may briefly interrupt the stable container name while health-checking

Related

• Dockerfile App site type
• Environment variables
• Rollback & history