Docker Logo Docker-Compose.net

Docker Compose for tomsquest/docker-radicale

Generated docker-compose.yml ready to deploy. Tweak indentation, volume bindings, or convert another command below.

$
Quick Try:
Public ID: mu4fn6le
Docker Hub
docker-compose.yml
Download Raw
Try on Play-With-Docker
WGET:

How to Convert Docker Run to Docker Compose

Migrate from imperative terminal commands to declarative multi-container infrastructure in 3 simple steps.

1

Paste Docker Run Command

Enter any standard docker run command containing port mappings (-p), volumes (-v), environment variables (-e), restart policies, and network modes.

2

Automated YAML Parsing

Our parser translates Docker CLI flags into standardized docker-compose.yml syntax. Customize indentation spacing (2s, 4s, 6s) or toggle external volume declarations with one click.

3

Deploy with Compose

Save the output as docker-compose.yml in your project folder, or fetch it via wget/curl. Start your containerized service instantly with docker compose up -d.

Docker Run Flags to Compose Property Reference

Comprehensive guide to how common Docker CLI flags map directly to Docker Compose definitions.

Docker CLI Flag Docker Compose Key Compose Syntax Example
-p, --publish ports ports:
  - "8080:80"
-v, --volume volumes volumes:
  - ./data:/var/lib/data
-e, --env environment environment:
  - NODE_ENV=production
--env-file env_file env_file:
  - .env
--name container_name container_name: web_service
--restart restart restart: unless-stopped
--net, --network network_mode network_mode: host
--privileged privileged privileged: true
--gpus deploy.resources.reservations.devices deploy:
  resources:
    reservations:
      devices:
        - driver: nvidia
          count: all
--ulimit ulimits ulimits:
  nofile:
    soft: 262144
    hard: 262144
--mount volumes volumes:
  - type: bind
    source: ./logs
    target: /app/logs

Frequently Asked Questions

Everything you need to know about Docker Run to Docker Compose conversion.

docker run is an imperative command used to start a single container from the terminal. Docker Compose uses a declarative YAML configuration file (docker-compose.yml) to define, configure, and orchestrate multiple containers, networks, volumes, and secrets together with version-controllable reproducibility.
You can inspect any running container on your host by running:

docker inspect --format "$(curl -s https://run.docker-compose.net)" YOUR-CONTAINER-ID

This will generate the original docker run command for that container, which you can paste directly into docker-compose.net to create your docker-compose.yml file.
Yes! Simply toggle the Private switch next to the generator button. When marked private, your snippet will not be indexed in the public sitemap (sitemap.xml) and won't appear in public directory listings.
Convert each container first to obtain its unique Compose ID (e.g., rc4tbg and rc4tat). Then enter the secondary ID into the Merge ID field in the toolbar, or navigate directly to https://docker-compose.net/rc4tbg+rc4tat to combine both services into one unified multi-container YAML file.
Docker Compose resolves volume paths relative to the directory containing the docker-compose.yml file itself. Bash environment substitutions like $(pwd) or `pwd` are not evaluated by Compose. Instead, use relative paths such as ./logs:/app/logs or standard named volumes.