About Decomposerize
The reverse of Composerize: paste a
docker-compose.yml and get the equivalent
docker run command(s) back. Useful when you want to test
a single container without spinning up compose, or when the tutorial
you're following happens to be in the other format.
Each service becomes its own run command with the right flags. It's also a decent way to see what Compose is actually doing under the hood — the raw flags it maps your YAML to.
All in the browser; nothing leaves your machine.
How to use Decomposerize
Paste your docker-compose.yml into the input to generate docker run commands. Copy the command for the service you want to test and review its ports, volumes, and environment variables before running it.
For a service with image: nginx and ports: ["8080:80"], the corresponding port mapping is docker run -p 8080:80 nginx. Generated commands may include additional options from your Compose file.
Compose can coordinate multiple services. Review shared networks, named volumes, and service dependencies separately when running containers with individual commands.
Frequently Asked Questions
What is Decomposerize?
Decomposerize reverses Composerize: it takes an existing docker-compose.yml file and translates it back into one or more docker run commands.
When would I convert compose back to docker run?
Common reasons: quickly testing a single container without setting up compose, debugging on a server where docker compose is not available, translating tutorials between the two formats, or comparing how compose maps to raw flags.
Does it support multiple services in one compose file?
Yes. Each service in the compose file is emitted as its own docker run command, including its ports, volumes, environment variables, networks and health checks.
Is the conversion private?
Yes. Everything happens in your browser securely. Your compose file, including any secrets or environment values, never leaves your device.