Docker Compose Creator
Create a file docker-compose.yml valid with the visual builder. Add services from the catalog, configure ports, environment variables, volumes, and dependencies. No external dependency - everything in-browser.
Aggiungi servizio dal catalogo
Nessun servizio aggiunto
Clicca su un servizio nel catalogo per aggiungerlo alla configurazione.
Aggiungi almeno un servizio per generare il file
Come utilizzare Docker Compose Generator
Add services from the catalog
Browse our library of 14 pre-configured services (PostgreSQL, MySQL, Redis, MongoDB, RabbitMQ, Nginx, Node.js, Python, Java/Spring Boot, Elasticsearch, MinIO, Grafana, Prometheus, Loki) and click to add them to your stack.
Customize doors, environment variables and volumes
Expand all added services to modify name, image/tag, restart policy, door mapping, environment variables and mounted volumes, or add new voices with dedicated buttons.
Configure service dependencies
For each service you can select which other services in the stack should wait for startup (depends_on).
Generate, copy or download the docker-compose.yml file.
Choose syntax version, compose a name for the network, then generate the file. Copy to notes or download directly as docker-compose.yml ready for "docker compose up -d".
Suggerimenti
- Use short and consistent service names (e.g., "db", "cache", "api"): they become the network hostnames reachable from other containers in the same stack.
- Configure always "depends_on" for services with strong dependencies (e.g., backend that needs the database), but remember it doesn't wait for the actual "ready" state of the service, only the container startup.
Domande frequenti
What services are available in the catalog?
14 pre-configured services: database (PostgreSQL, MySQL, MongoDB), cache (Redis Stack), messaging (RabbitMQ), proxy (Nginx), runtime applications (Node.js, Python, Java/Spring Boot), search (Elasticsearch), storage (MinIO) and monitoring (Grafana, Prometheus, Loki), each with ports, environment variables, and typical volumes already set as a starting point.
What difference is there between available Compose versions (3.8, 3.9, Compose V2)?
3.8 and 3.9 add a line "version:" explicitly at the start of the file (legacy Compose V1 syntax). "Compose V2 (without version)" omits this line, as recommended by recent Docker Compose versions that ignore or deprecate the version field.
How are volumes named with respect to bind mounts?
If the host path of a volume does not start with either "." or "/" (e.g., "postgres_data"), the tool recognizes it as a Docker volume with name and automatically declares it in the "volumes:" section of the generated file. Paths starting with "./" or "/" remain bound mounts to the host filesystem.
What happens if I remove a service that others depend on?
The tool automatically removes references to "depends_on" for the deleted service from other services in the stack, to avoid generating a YAML with dependencies towards containers that no longer exist.
Are environment variables' passwords and default values secure for production?
No pre-filled values (e.g. "mypassword", "rootpassword", "minioadmin") are only placeholder values intended for local development environments. Always replace them with strong credentials managed through Secret Manager or external environment variables before using the file in production.