Import from Docker Compose
Right-click the canvas and choose Import (docker run, compose, link)…. Paste or link any of:
- a
docker-compose.ymlfile (or a link to one) - a
docker run …command - a Dockerfile, an image name, or a Docker Hub page
ZedCloud shows each service it found with a checkbox, the values it still needs, warnings, and an estimate of memory. Pick what to keep and import. Several services land in one group named after the project, staged until you Deploy.
When a build finds compose files in your repository, the build row offers Import as nodes… too.
How services are mapped
Section titled “How services are mapped”| In the compose file | Becomes |
|---|---|
postgres, postgis, pgvector, timescale |
A managed Postgres node |
redis, valkey, keydb, dragonfly |
A managed Valkey node |
Anything else (including mysql, mongo) |
An app running that image |
Managed nodes come with accounts and links, so the apps get DATABASE_URL and friends instead of hard-coded passwords.
What isn’t imported
Section titled “What isn’t imported”commandandentrypointoverrides: the image’s own start command is used.- Bind mounts and host ports.
- Profiles.
Services that need privileged, host networking or PID, extra capabilities, devices, or the Docker socket are
refused. Up to 30 services and 200 variables per service.