Docker Service
Deploy pre-built Docker images like databases, caches, and other infrastructure components
The docker service type deploys pre-built Docker images without building from source. This is ideal for databases, caches, message queues, and other infrastructure components.
Examples
PostgreSQL database (internal only):
Reference from other services:
Fields Reference
Required Fields
| Field | Type | Description |
|---|---|---|
dockerImage | string | Docker image name (e.g., postgres, redis) |
defaultTag | string | Image tag (e.g., 15-alpine, 7-alpine) |
Optional Fields
| Field | Type | Description |
|---|---|---|
command | string | Override container entrypoint |
arguments | string | Arguments passed to the command. Use %%SPLIT%% for spaces |
env | object | Environment variables |
ports | array | Exposed container ports |
deployment | object | Deployment configuration (see below) |
envLens | boolean | Enable environment lens ingress banner |
Deployment Options
The deployment section configures how the service is deployed to Kubernetes. All fields are optional.
See GitHub Service - Deployment Options for detailed documentation of each field.
| Field | Description |
|---|---|
public | true = creates ingress, false = internal only |
capacityType | Node type: spot or on-demand |
resource | CPU and memory requests/limits |
readiness | Health check using httpGet or tcpSocketPort |
hostnames | Custom hostname config (auto-constructed from global_config if omitted) |
network | IP whitelist, port mapping, gRPC support |
serviceDisks | Persistent volume mounts |
For databases and caches, you typically want public: false to keep them
internal to the cluster.