Importing Docker Compose

Orbit reads a Compose file from a repository (compose.yaml, compose.yml, docker-compose.yml or docker-compose.yaml at the root, or a path you give) or from a pasted or uploaded file, and shows a plan to review before anything is created.

What it creates

• Databases: PostgreSQL, MySQL (and MariaDB) and Redis (and Valkey) images become managed databases on the version Orbit runs. They start empty: data in the Compose volumes is not migrated. Back it up with the old setup and restore it into the new database if you need it.
• Applications and workers: a service with a port becomes an application, without one a worker. A build: at the repository root with its Dockerfile is built by Orbit from the repository. Anything else needs a container image, which the review asks for.
• Variables: they are copied, and names that look secret become secrets. Values that point to a database become references, and URLs that point to another service are rewritten to its address inside the environment.

What it does not keep

Application volumes, env_file, networks, privileged, capabilities, devices, Compose secrets and configs. The review lists each one, and instances are set in Settings afterwards.

After the import

Each service is an ordinary application, worker or database. Nothing ties them to the file anymore, so later changes to it are not picked up.