Which docker run flags are converted automatically?

The common ones: --name, -p port mappings, -v volume mounts, -e environment variables, --restart, --network and the image tag. Each maps to the corresponding compose service field. Flags that describe orchestration (health checks, network aliases, swarm constraints) are not covered and should be added manually in the generated YAML.

Can I paste a command with line continuations or extra whitespace?

Yes. The parser tolerates backslash line continuations and irregular spacing, so a multi-line command copied from a README converts the same as a single-line one. Flags with values are matched by name, not by position.

Does the generated compose file work with docker compose v2?

Yes. The output uses the standard service fields (image, ports, volumes, environment, restart) that both docker compose v2 and Compose V2-compatible tools understand. Always run docker compose config or start the stack once before committing the file — the tool converts syntax, it cannot validate that your actual image and paths exist.

Docker Run to Compose Converter — Guide

Transforms "docker run" commands into docker-compose files!

What it is and when to use it

Containerising a service by hand means a docker run command on the whiteboard and a compose file in the repo — two sources that drift apart. This tool reads a docker run command and emits the equivalent docker-compose.yml service entry: the image and container name, published port mappings, volume mounts, environment variables and restart policy all carry over, so the command you tested locally becomes version-controlled infrastructure. The generated YAML is a starting point, not a substitute for review: automatic conversion covers the common flags, while health checks, network aliases, depends_on ordering and multi-service wiring still need to be added by hand — the tool makes the mechanical 80% instant so you can spend attention on the part that actually needs judgement.

Turns a long docker run command into a docker-compose.yml, saving you from writing the compose file by hand.

How to use it

Paste the docker run command
The compose snippet is generated on the right
Check the port mappings and volume mounts before copying

A worked example

Fill in a sample command

docker run -d --name web -p 8080:80 -v /data:/usr/share/nginx/html nginx:latest

Copy this into the tool, or open Docker Run to Compose Converter

Things that trip people up

Automatic conversion covers the common flags; health checks, network aliases and similar need to be added by hand

Questions people ask

Which docker run flags are converted automatically?: The common ones: --name, -p port mappings, -v volume mounts, -e environment variables, --restart, --network and the image tag. Each maps to the corresponding compose service field. Flags that describe orchestration (health checks, network aliases, swarm constraints) are not covered and should be added manually in the generated YAML.
Can I paste a command with line continuations or extra whitespace?: Yes. The parser tolerates backslash line continuations and irregular spacing, so a multi-line command copied from a README converts the same as a single-line one. Flags with values are matched by name, not by position.
Does the generated compose file work with docker compose v2?: Yes. The output uses the standard service fields (image, ports, volumes, environment, restart) that both docker compose v2 and Compose V2-compatible tools understand. Always run docker compose config or start the stack once before committing the file — the tool converts syntax, it cannot validate that your actual image and paths exist.

Next steps

Open the Docker Run to Compose Converter tool

Spotted something wrong on this page? Tell us via Contact Us