Development
.env Parser & Editor
Parse, inspect, validate, search and export environment variable files.
NewLocal
Development
Docker Run to Compose
Convert docker run commands into Docker Compose YAML.
Docker run command
Paste a docker run command to convert common options into a Compose service.
Convert a Docker command
Paste a docker run command and select Convert to Compose to generate a Compose service.
Docker commands are parsed locally inside your browser. BigForgeKit does not execute the command, contact Docker or upload environment values.
About this tool
What is Docker Run to Compose?
Docker Run to Compose converts a docker run command into a structured Compose service. It extracts the image, container name, published ports, mounted volumes, environment variables, labels and other common options while reporting flags that require manual review.
Features
Built for fast developer workflows
- Convert single-line and multiline docker run commands.
- Extract Docker images and container names.
- Convert published TCP and UDP ports.
- Convert bind mounts and named volumes.
- Generate top-level named volume declarations.
- Convert environment variables and labels.
- Support restart policies, working directories and entrypoints.
- Support users, hostnames, networks and privileged mode.
- Preserve command arguments following the image.
- Report unsupported or non-equivalent options.
- Copy or download the generated compose.yaml file.
- Parse every command locally inside your browser.
Frequently asked questions
Questions about Docker Run to Compose
Does the converter execute the Docker command?
No. The command is only parsed locally and is never executed.
Which docker run options are supported?
The converter supports common options including name, restart, ports, volumes, environment variables, labels, working directory, entrypoint, hostname, user, network and privileged mode.
Are all docker run options equivalent to Compose?
No. Some runtime flags do not map directly to a persistent Compose service. These options are shown as warnings for manual review.
Are named volumes declared automatically?
Yes. Named volumes used by the service are also added to the top-level volumes section.
Are environment values uploaded?
No. Docker commands and environment values remain inside your browser.
Should I review the generated YAML?
Yes. Always review generated Compose configuration before using it in development or production.
Related tools