Docker Resources - Openinary Docs

docker-compose.yml reads these four variables to constrain the container. Pick the row that matches your server and move on.

Server	CPU limit	Memory limit	CPU reservation	Memory reservation
1-2 GB, images only	`1.0`	`2G`	`0.25`	`512M`
4 GB (default)	`2.0`	`4G`	`0.5`	`1G`
16 GB, video-heavy	`4.0`	`12G`	`1.0`	`2G`

DOCKER_CPU_LIMIT=2.0
DOCKER_MEMORY_LIMIT=4G
DOCKER_CPU_RESERVATION=0.5
DOCKER_MEMORY_RESERVATION=1G

A container that exceeds DOCKER_MEMORY_LIMIT is OOM-killed. Video processing is memory-hungry: give it at least 2 GB, and 4 GB if you encode anything large. Below 2 GB, video jobs fail and the deployment is image-only.

What each one does

Variable	Default	Description
`DOCKER_CPU_LIMIT`	`2.0`	Hard cap in cores. The container never exceeds it, even on an idle host
`DOCKER_MEMORY_LIMIT`	`4G`	Hard cap. `G` for gigabytes, `M` for megabytes
`DOCKER_CPU_RESERVATION`	`0.5`	Cores guaranteed when the host is under load
`DOCKER_MEMORY_RESERVATION`	`1G`	Memory guaranteed. Must be below the limit

The 16 GB row matches the commented block in docker.env.example, and adds VIDEO_MAX_CONCURRENT=4. That pairing matters: DOCKER_CPU_LIMIT is what caps video worker auto-detection, so raising memory alone buys you no extra workers.

Video Processing

Worker concurrency, retries and encode limits.

Deploy on Coolify

Full deployment guide with resource configuration.