Skip to content

Latest commit

 

History

History
43 lines (33 loc) · 2.7 KB

File metadata and controls

43 lines (33 loc) · 2.7 KB

Configuration

Documentation index

Environment variables

Variable Default Purpose
TZ Europe/Berlin Container timezone
CP_PORT 8080 Internal HTTP or HTTPS port
CP_ADMIN_USER admin Initial administrator username
CP_ADMIN_PASSWORD_FILE /run/secrets/admin_password Initial password secret file
CP_SCAN_INTERVAL_MINUTES 60 Initial scan interval
CP_AUTO_DEFAULT false Default automatic-update policy for new containers
CP_HEALTH_TIMEOUT_SECONDS 120 Maximum healthcheck wait
CP_STARTUP_GRACE_SECONDS 5 Stability window without a healthcheck
CP_SECURE_COOKIE false Adds the Secure attribute to session cookies
CP_TLS_CERT_FILE unset PEM certificate or full-chain file; enables native HTTPS together with CP_TLS_KEY_FILE
CP_TLS_KEY_FILE unset PEM private-key file for native HTTPS
CP_TLS_KEY_PASSPHRASE_FILE unset Optional file containing the private-key passphrase
CP_STORE_FILE /data/state.json Persistent state path
DOCKER_SOCKET /var/run/docker.sock Docker API socket
CP_SELF_UPDATE_REPOSITORY DeepZone/container-pilot GitHub release source
CP_SELF_UPDATE_IMAGE ghcr.io/deepzone/container-pilot Release image repository
CP_SELF_UPDATE_CHANNEL stable stable or prerelease
CP_REGISTRY_CREDENTIALS_FILE unset Docker Secret JSON for private registry pull credentials
CP_WEBHOOK_TOKEN_FILE unset Docker Secret containing an optional webhook bearer token
CP_ALLOW_INSECURE_WEBHOOK false Allow HTTP webhook URLs for trusted development environments only

Settings changed in the Web UI are persisted in /data/state.json and take precedence over initial scheduling defaults.

Roles

  • admin: scans, updates, rollbacks, policies, settings, and user management
  • viewer: read-only access to status and event history

Per-container policy

Automatic installation requires both global automatic installation and the individual container policy. Automatic updates retain the configured tag and never switch a container to latest.

Webhook enablement and its non-secret HTTPS URL are stored with the settings. Registry credentials and webhook bearer tokens are file-only secrets and are never persisted in the state store. See Webhook notifications and Private registries.

Native HTTPS requires both certificate and private-key files. Container Pilot refuses to start when only one is configured. When native HTTPS is enabled, session cookies automatically receive the Secure attribute. See Reverse proxy and HTTPS.