Skip to content
TextArray1.41.0
100% local

docker run to Compose

Convert a docker run command into a docker-compose.yml service, or the other way round.

Input
Output
Related tools
cURL to code converterDeveloper tools
YAML ⇄ JSON converterDeveloper tools
EditorConfig generatorRandom generators
i18n key diffDeveloper tools
TOML to JSON converterDeveloper tools
SQL to JSONDeveloper tools
docker run to Compose
Paste a docker run command and this tool rewrites it as a docker-compose.yml service, with the image, ports, volumes, environment variables, network and restart policy mapped to their compose equivalents. Flip the direction option and it works the other way too: paste a compose file and get back the equivalent docker run command for each service, useful when you only have a compose file but need to reproduce one container manually.
Paste more than one docker run command, one per line, and each becomes its own service in the same compose file — handy for turning a handful of ad-hoc containers into a proper multi-service stack. Recognized switches include -p/--publish, -v/--volume, -e/--env, --network, --restart, --memory and --cpus (mapped to a deploy.resources.limits block), plus --name, --workdir, --user, --entrypoint, --label and --hostname. Environment variables can stay inline under environment: or be moved into a generated .env file referenced with env_file:, and the compose file format can be written with or without a version: key.
Not every docker run flag has a compose equivalent — things like --rm or --pull are container lifecycle switches with no per-service compose setting. The tool never drops them silently: unsupported flags are listed as comments next to the service they belong to, so you can see exactly what didn't carry over. Turning off "preserve original flag order" sorts each list (ports, volumes, environment) alphabetically instead of keeping the order you typed them in, which can make a generated diff easier to review.
Everything runs locally in your browser — no command, image name or environment variable is ever sent anywhere. Copy the result, download it as a .txt file, or send the output back into the input to keep refining it.
FAQ
Can I convert several docker run commands at once?
Yes. Paste one docker run command per line (or use a trailing backslash to continue a command across lines) and each becomes a separate service in the generated compose file.
What happens to flags compose cannot express, like --rm?
They are not silently dropped. Each unsupported flag is listed as a comment next to the service it belongs to, so you know exactly what wasn't converted.
Does it also convert docker-compose.yml back into docker run commands?
Yes. Switch the direction option to "compose → docker run" and paste a compose file; the tool prints one docker run command per service.
Why would I put environment variables in a separate .env file instead of the compose file?
It keeps secrets and per-environment values out of version control when the compose file itself is committed. Choose "Separate .env file" and the tool moves the variables there and references them with env_file:.
Is my command or compose file uploaded anywhere?
No. The conversion runs entirely in your browser using JavaScript — nothing you paste ever leaves your device.