The docker run to Docker Compose converter — and back.

Paste the full docker run command into this docker run to compose converter with the mode set to run → compose, then press Convert. It strips the leading docker run, classifies each flag onto a service object, treats the first non-flag token as the image and the rest as the command, and prints a ready-to-use docker-compose.yml services: block — no install, no Docker daemon, and nothing pushed anywhere. The whole convert docker run to docker-compose.yml flow happens in the browser.

Yes — this is a bidirectional docker run / docker compose converter. Switch the mode toggle to compose → run, paste a service definition (or a full Compose file — the first service is used), and it reconstructs an equivalent docker run command, including ports, volumes, environment, networks, capabilities, resource limits and a healthcheck. This docker compose to docker run command converter reports keys with no docker run equivalent — depends_on, build, deploy, profiles — as warnings rather than translating them.

The common docker run flags map cleanly: -p/--publish → ports, -v/--volume and --mount → volumes, -e/--env → environment, --env-file → env_file, --name → container_name, --restart → restart, --network/--net → networks (or network_mode for host/none), -w/--workdir → working_dir, -u/--user → user, --entrypoint → entrypoint, --hostname → hostname, --add-host → extra_hosts, --cap-add/--cap-drop → cap_add/cap_drop, --privileged → privileged, -m/--memory → mem_limit, --cpus → cpus, -l/--label → labels, and the --health-* flags → a healthcheck block. -i and -t map to stdin_open and tty.

Each -p / --publish flag becomes an entry under the ports: list in the Compose service, written as a quoted "HOST:CONTAINER" string — so docker run -p 8080:80 turns into a ports entry of "8080:80". The converter quotes the value because YAML would otherwise read a bare 8080:80 as a sexagesimal number, which is exactly the kind of subtle bug that hand-conversion of docker run -p -v -e to compose tends to introduce.

Every -v / --volume (and --mount) flag is collected into the volumes: list on the service, keeping the short source:target[:ro] form, so docker run -v /data:/usr/share/nginx/html:ro becomes a volumes entry of /data:/usr/share/nginx/html:ro. Named volumes and bind mounts are preserved as written; the tool does not invent a top-level volumes: section you did not ask for.

Each -e / --env flag becomes a KEY=value entry under environment: in the service, and any --env-file is mapped to env_file:. Because the conversion is docker run to compose yaml with no upload, you can safely paste commands whose -e flags carry secret-bearing values or internal hostnames — they are tokenised in your browser and never sent anywhere.

The docker run restart policy maps straight to the restart: key in Compose: --restart no, --restart always, --restart on-failure[:max] and --restart unless-stopped are carried across unchanged. So docker run --restart unless-stopped becomes restart: unless-stopped in the generated service.

Yes. It is a free docker run to compose converter that runs 100% client-side, so it works as a docker run to compose converter that runs in the browser — there is no server, no account and no signup, and once the page has loaded it keeps working with no network. That also makes it a docker run to docker compose converter with no install: nothing is uploaded and nothing is installed on your machine.