Quick start

Run the Docker image

The easiest way to start is to deploy the official drydock image.

Using a socket proxy is the most secure way to expose the Docker API. The proxy limits which endpoints Drydock can access.

services:
  drydock:
    image: codeswhat/drydock
    container_name: drydock
    depends_on:
      - socket-proxy
    environment:
      - DD_WATCHER_LOCAL_HOST=socket-proxy
      - DD_WATCHER_LOCAL_PORT=2375
    ports:
      - 3000:3000

  socket-proxy:
    image: tecnativa/docker-socket-proxy
    container_name: drydock-socket-proxy
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - CONTAINERS=1
      - IMAGES=1
      - EVENTS=1
      - SERVICES=1
      # Add POST=1 and NETWORKS=1 if using the Docker trigger for auto-updates
    restart: unless-stopped

The simplest setup — mount the Docker socket directly. Works out of the box on most systems.

services:
  drydock:
    image: codeswhat/drydock
    container_name: drydock
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 3000:3000

If you need a read-only socket mount (:ro), set DD_RUN_AS_ROOT=true to skip Drydock's privilege drop. See the Docker Socket Security section for details.

docker run -d --name drydock \
  -v "/var/run/docker.sock:/var/run/docker.sock" \
  -p 3000:3000 \
  codeswhat/drydock

The official image is published on Github Container Registry: codeswhat/drydock

Open the UI

Open the UI in a browser and check that everything is working as expected.

Add your first trigger

Everything ok? It's time to add some triggers!

Going deeper

Need to fine configure how drydock must watch your containers? Take a look at the watcher documentation!

Need to integrate other registries (ECR, GCR...)? Take a look at the registry documentation.

Ready-to-go examples

You can find here a complete configuration example illustrating some common drydock options.