FREE TOOL

Check your docker-compose.yml before you move it.

Paste a Compose file and see where each service goes on DeployVera: which parts become applications, which become managed databases, and which cannot be migrated as written, with the reason. DeployVera does not run Compose files as they are; this check shows how to split yours.

Your file is processed in your browser. Nothing is uploaded, stored or sent anywhere.

Up to 200 KB. Even though nothing leaves your browser, remove real passwords and keys before pasting.

Next steps

  1. Give each service that has a build: its own Git repository with a Dockerfile, and deploy each one as a separate application.
  2. Create a managed database in place of each database service, copy the connection from the panel and add it to the application's environment variables.
  3. Replace addresses that use service names with the internal dv- addresses the panel shows.

The number of applications and databases depends on your plan; check your plan's limits before you create the services.

We will go through the first setup together.

Write to us to adapt your project; attach your Compose file and repository link. The team helps with the first setup.

What the check looks at

The analysis is a static read of your file in the browser. It does not build, start or contact anything. It looks at:

  • Service type: a service with build: becomes an application; postgres, mysql, mongo and redis images become managed databases; any other image is flagged.
  • Settings that cannot be carried over: privileged, host networking, host namespaces, extra Linux capabilities, devices, the Docker socket and unconfined security options.
  • Volumes and data: host folder mounts are not supported, and data in named volumes does not move with the project.
  • Ports: an application listens on one port; several published ports are flagged.
  • Wiring: environment variables that use another service's name as the host, depends_on, env_file, healthcheck and restart.
  • Features it cannot resolve: extends, include, configs and secrets.

Example input and result

Pasting this file shows three services.

docker-compose.yml

services:
  web:
    build: .
    ports:
      - "3000:3000"
    environment:
      DATABASE_URL: postgres://app:password@db:5432/app
  db:
    image: postgres:16
  worker:
    build: ./worker
    privileged: true

Result

  • web: application, port 3000. Its DATABASE_URL uses the service name db; you replace it with the internal address the panel shows.
  • db: managed PostgreSQL. Its data does not move; dump and import it.
  • worker: application, blocked. privileged: true is not supported, and its build context is not at the repository root.

Why Compose is not run as it is

User-supplied Compose files can request privileged containers, host networking or host mounts; not safe on a multi-tenant server.

Instead, split the file into separate applications and managed databases inside one service; the migration guide describes each step.

Frequently asked questions

Is my docker-compose.yml uploaded anywhere?

No. The file is analysed in your browser. Nothing is uploaded, stored or sent to a server, so you can paste a real file.

Will my docker-compose.yml run on DeployVera as written?

No. DeployVera does not run Compose files as they are. The check shows how to split yours into applications and managed databases.

Which databases become managed databases?

Services using a PostgreSQL, MySQL, MongoDB or Redis image. These managed databases are still in beta, and Redis data is not guaranteed to persist to disk.

What does a blocker mean?

A blocker is a setting that cannot be carried over, such as privileged mode, host networking or a host folder mount. Remove it or redesign that part before you move the service.

Does "No blockers found" mean the project will deploy?

No. It is a static check. It does not build the image, test the ports or secrets, or confirm that your plan has enough capacity.

How many applications and databases can I run?

That depends on your plan. The free plan has one application; prices and limits of the paid plans are in the live catalog on the Docker plans page.