Docker Run to Compose Converter

docker run is the CLI command for starting a single Docker container with all its configuration specified as flags. While powerful for quick testing, long docker run commands become hard to read, share, and reproduce. Docker Compose solves this by letting you define container configuration in a declarative docker-compose.yml file that can be version-controlled and shared with your team. Our docker run to Compose converter bridges the gap: paste any docker run command and instantly get the equivalent docker-compose.yml service block. This is especially useful when migrating from ad-hoc container management to a proper Compose-based workflow.

1. 1. Paste Your docker run Command: Copy any docker run command — from documentation, a shell script, or your terminal history — and paste it into the input. Multi-line commands with backslash continuation (\) are supported automatically.
2. 2. Click Convert to Compose: Click the Convert button. The converter parses all docker run flags and generates a clean, properly indented docker-compose.yml service block. Named volumes and custom networks are automatically added to the top-level volumes: and networks: sections.
3. 3. Copy or Download: Copy the generated YAML to your clipboard or download it as docker-compose.yml for immediate use in your project.

• Image & Container Name: The image name and tag map to image:. The --name flag maps to container_name: and is also used as the Compose service name.
• Port Mappings: Each -p host:container flag maps to an entry in the ports: list. Port ranges and protocol suffixes (e.g., :udp) are preserved as-is.
• Volumes: Each -v flag maps to an entry in the volumes: list. Named volumes (without a leading / or .) are automatically added to the top-level volumes: section.
• Environment Variables: Each -e KEY=VALUE flag maps to an entry in environment:. The --env-file flag maps to env_file:.
• Restart Policy: The --restart flag maps to restart:. The on-failure:N form also generates a deploy.restart_policy block with max_attempts.
• Networks: Custom --network values map to the networks: list and are added to the top-level networks: section as external networks.

• -d, --detach — Silently ignored (Compose services run detached by default)
• --name — Maps to container_name: and used as the service name
• -p, --publish HOST:CONTAINER — Maps to ports: list entries
• -v, --volume HOST:CONTAINER — Maps to volumes: list entries; named volumes added to top-level volumes:
• -e, --env KEY=VALUE — Maps to environment: key-value pairs
• --env-file FILE — Maps to env_file: list entries
• --network NETWORK — Maps to networks: list; added to top-level networks: as external
• --restart POLICY — Maps to restart: (no, always, unless-stopped, on-failure)
• -l, --label KEY=VALUE — Maps to labels: key-value pairs
• --entrypoint CMD — Maps to entrypoint:
• -w, --workdir PATH — Maps to working_dir:
• -u, --user USER — Maps to user:
• -h, --hostname NAME — Maps to hostname:
• --privileged — Maps to privileged: true
• --read-only — Maps to read_only: true
• -t, --tty — Maps to tty: true
• -i, --interactive — Maps to stdin_open: true
• --cap-add CAP — Maps to cap_add: list
• --cap-drop CAP — Maps to cap_drop: list
• --device PATH — Maps to devices: list
• --dns IP — Maps to dns: list
• --add-host HOST:IP — Maps to extra_hosts: list
• --shm-size SIZE — Maps to shm_size:
• -m, --memory LIMIT — Maps to mem_limit:
• --cpu-shares N — Maps to cpu_shares:
• --health-cmd CMD — Maps to healthcheck.test with default interval/timeout/retries
• --log-driver DRIVER — Maps to logging.driver:
• --log-opt KEY=VALUE — Maps to logging.options: key-value pairs
• --security-opt OPT — Maps to security_opt: list
• --ulimit TYPE:SOFT:HARD — Maps to ulimits: section
• --tmpfs PATH — Maps to tmpfs: list