A ready-to-use collection of common development services (databases, caches, queues, and more) managed through Docker Compose. Run all your shared services from one place instead of duplicating them across every project.

When working on multiple projects at the same time, each project often comes with its own set of services like MySQL, Redis, or RabbitMQ. Running duplicate copies of the same service wastes system resources and makes it hard to keep track of ports and configurations.

Docker Commons solves this by letting you:

• Run shared services (databases, caches, queues, etc.) once and connect any project to them.
• Pick only the services you need — no need to start everything.
• Use simple network aliases (e.g. common-mysql, common-redis) so your apps can find services easily.
• Keep all service settings in one place, making them easy to update.

Inspired by LaraDock.

Each service that needs extra setup or has special instructions has its own documentation inside its folder. See the links in the Services table below.

Below is the full list of services included in this project. The Compose Name is what you use in docker compose up -d <name> commands. The Network Alias is the hostname your application uses to connect to the service.

• Elasticsearch & Kibana — Require a custom image build. On first start, Elasticsearch generates a password you will need. See Elasticsearch Docs for details.
• Cassandra DSE — Runs as a multi-node cluster (3 nodes). Default credentials are cassandra / cassandra. See Cassandra DSE Docs.
• NFS Server — After starting, you must mount the NFS share on your host. See Service Specific Details below for commands.
• Apache Druid — Requires Apache Zookeeper to be running. Start both together: docker compose up -d zookeeper apache_druid_coordinator apache_druid_broker apache_druid_historical apache_druid_middlemanager apache_druid_router.

• Fully supported. All services work natively.
• Use copy-examples.sh to create configuration files.
• Use : as the path separator in the .env file for COMPOSE_PATH_SEPARATOR.

• Supported. Use bash copy-examples.sh to create configuration files.
• Use : as the path separator in the .env file for COMPOSE_PATH_SEPARATOR.

• Use copy-examples.bat to create configuration files.
• Use ; as the path separator in the .env file for COMPOSE_PATH_SEPARATOR.
• If your system supports WSL2, it is highly recommended to use that instead of running Docker directly on Windows.
• The following services do not work on a Windows host and require WSL2:
  • NFS Server

• Docker Engine v20.10+ / Docker Desktop v4.0+
• Docker Compose v2.7+ (Use docker compose command)
  • or v1.29+ (Use docker-compose command)

1. Open a terminal or command prompt.
2. Clone this repository and cd into the directory. Opening it in an IDE is helpful.
3. Create configuration files from the provided examples. Run the appropriate script for your OS (see Operating System Notes above), or copy the files manually. Do not delete the example files — they are kept for reference.
   • .env.example → .env
   • docker-compose.override.example.yml → docker-compose.override.yml
   • .envs/{name}.example.env → .envs/{name}.env
4. Edit .env and update values for your environment:
   • COMPOSE_FILE — List the docker-compose.override.{name}.yml files for the services you want. Keep docker-compose.override.yml at the end.
   • COMPOSE_PATH_SEPARATOR — Use : on Linux/macOS or ; on Windows.
   • Other settings are documented as comments inside the file.
5. Edit docker-compose.override.yml:
   • Remove service sections you do not need.
   • Adjust any settings as required.
6. Edit files in .envs/{name}.env as needed for each service.
7. Pull the Docker images:

   docker compose pull

   If it stops due to a network error, just run it again.
8. Create the shared Docker network:

   docker network create common-net

9. (Optional) If using Traefik, create its network:

   docker network create common-traefik-net

10. (Optional) If using services that require a custom image build (see the Services table), build them:

    docker compose build <service-name>

• Start all services:

  docker compose up -d

• Start specific services only:

  docker compose up -d <service1> <service2> ...

  Example: docker compose up -d adminer mysql

• View running services:

  docker compose ps

• View logs for a specific service:

  docker compose logs --tail=100 <service-name>

• Stop all services:

  docker compose down

• Stop specific services only:

  docker compose rm -sf <service1> <service2> ...

  Example: docker compose rm -sf adminer mysql

Connect your application's Docker network to common-net and use the service's network alias as the hostname and the container port as the port number.

For example, to connect to MySQL, add this to your application's docker-compose.yml:

networks:
  common-net:
    external: true

services:
  myapp:
    ...
    networks:
      - common-net
      ...

Then in your application's database configuration:

• Host: common-mysql
• Port: 3306

Restart your application container and it will be able to reach MySQL. This same approach works for all services that have a network alias.

After starting the NFS container, mount it on your host machine. First find the container's IP (e.g. using ifconfig or hostname -I), then run:

sudo mount -v -o vers=4,loud <container-ip>:/ /path/to/mount

Important: Always unmount before shutting down your machine to avoid issues:

sudo umount /path/to/mount

This project is designed for local development. It can be adapted for production, but you may need to change security settings, use different images, or mount custom configuration files. Always review security concerns before deploying any of these services in a production environment.

• Make it work with Podman.

This project is licensed under the terms of the MIT License.