TECHNICAL REFERENCE
Adapt a Compose project to DeployVera
How to turn the services in a Docker Compose file into separate applications and managed databases.
Docker Compose is not supported yet
The panel does not run a Docker Compose file as written. A customer-written Compose file can ask for privileged containers, host networking or host folder mounts, which is not safe on a multi-tenant server.
Most Compose projects can be split into separate applications and managed databases inside one service. Applications and databases of the same service reach each other over a private network.
This section describes the default state. When restricted Compose support is switched on, the new-deployment wizard shows a "Docker Compose (restricted)" method; if you do not see it, Compose support is not enabled yet.
Restricted Compose support (when enabled)
When enabled, your Compose file is checked on the server before every deployment and only allowed options are accepted. The file must be in the repository root (docker-compose.yaml/yml or compose.yaml/yml) and come from GitHub, a connected GitLab or a connected Gitea repository. Up to 10 services, 100 KB and 50 YAML aliases are accepted. The domain is attached to the single service that exposes a port (expose).
Accepted: image or in-repository build, environment, expose, depends_on, healthcheck, restart, declared named volumes, tmpfs, CPU/memory limits and declared bridge networks.
Rejected: privileged, cap_add, devices, network_mode, host pid/ipc/uts/userns/cgroup, ports (use expose instead), extra_hosts, sysctls, container_name, links, host path mounts (absolute, relative ./ or .. paths and docker.sock included), external networks and volumes, a build context that leaves the repository, extends/configs/secrets/include, traefik/caddy/coolify labels and every unrecognised option. Each rejected rule is shown in the panel with its own explanation.
Preview password protection, PRIVATE access, static site mode, build directory and source migration are not available for Compose deployments.
Where each part goes
- A service built from your code (
build:): a separate application using the Dockerfile in the repository. Each application uses one application slot; the number of slots depends on your plan. redis,postgres,mysql,mongoimages: managed Redis, PostgreSQL, MySQL and MongoDB databases. The database quota is separate from the application quota.ports:: the single port the application listens on. Choose public access if it must be reachable from the internet, or private (PRIVATE) access if only other applications use it.environment:andenv_file:: the application's environment variables. Do not commit passwords or keys; enter them in the panel.- Service names (
http://api:3000,redis:6379): on the private network, addresses are internal addresses starting withdv-. The panel shows this address on the application detail page and for each database. Pass it to the other application as an environment variable. depends_on:: there is no start order. Your applications should retry when the service they depend on is not reachable yet.volumes:: not carried over. Use a managed database for persistent data.
Managed Redis
Redis can be chosen as an engine on the Databases page. Copy the connection value from the panel and add it yourself to the application's environment variables as REDIS_URL; the user name is default and the database number is 0.
Persistence of Redis data to disk is not guaranteed. Use it for cache, sessions and rebuildable queue data, not as the single source of truth. Redis has a memory limit; if it fills up, the process can stop and restart, so limit memory use in your application. There is no browser management screen for Redis.
What to know
- The panel has no build directory setting: to separate several services that live in one repository, give each service its own repository.
- Host networking, privileged containers and host folder mounts are not supported.
- The service's CPU, RAM and disk limit is shared by the applications inside it; each managed database also has its own memory and CPU limit.
Let's adapt it together
Open a support ticket or write through the contact page and attach your Compose file and repository link. We will go through the first setup together.
Before you move, you can paste your file into the free Compose compatibility check (/tools/compose-check). It runs in your browser; nothing is uploaded or stored.