Skip to content
ReverseDock

Dokploy, Coolify and Portainer

These platforms deploy applications as Docker containers and describe their routing with Traefik labels. With traefik_labels on (the default), the Docker provider since v0.2 reads those labels; what remains is joining the right network. The platform facts below come from each project’s documentation, checked 2026-10-28.

This is about reading the labels these platforms write. The platforms run and configure their own Traefik; replacing it inside the platform is up to each platform’s own settings.

Dokploy

Section titled “Dokploy”

Dokploy adds Traefik labels to Compose applications when you assign a domain, and attaches them to the dokploy-network network (Dokploy domains). Applications that are not Compose stacks get file configuration in Dokploy’s Traefik instead of labels, so ReverseDock does not see them.

rdock.yaml
listeners:
  web: { address: ":80" }


defaults:
  listeners: [web]
  tls: off


providers:
  docker:
    network: dokploy-network

Put ReverseDock on dokploy-network (it is created by Dokploy; declare it external: true in ReverseDock’s Compose file). Containers are only read with traefik.enable=true; if the labels Dokploy writes do not include it, set expose_by_default: true, which reads every container on the host, so check rdock status for what that adds.

Coolify

Section titled “Coolify”

Coolify writes router, middleware, service and port labels for each resource and marks its containers with coolify.managed=true (Coolify and Traefik). Resources that are not Compose files use the coolify network; each Compose resource gets a network of its own that the proxy joins (Networking in Coolify).

rdock.yaml
listeners:
  web: { address: ":80" }


defaults:
  listeners: [web]
  tls: off


providers:
  docker:
    network: coolify

Connect ReverseDock to coolify, and to each Compose resource’s network you want routed (docker network connect <network> rdock). A container on several networks needs traefik.docker.network or providers.docker.network to choose; otherwise it is reported and not routed.

Portainer

Section titled “Portainer”

Portainer creates no shared network and adds no labels: you write the labels in the stack yourself (Portainer and Traefik). Create a network once and use it in every stack:

Terminal window
docker network create proxy
stack.yaml
services:
  app:
    image: traefik/whoami:v1.11.0
    labels:
      rdock.enable: "true"
      rdock.host: app.example.com
      rdock.tls: "off"
    networks: [proxy]


networks:
  proxy:
    external: true

Deploy ReverseDock itself as a stack on the same network, with the setup from Docker containers and labels. Portainer’s Swarm stacks use deploy.labels, which the Swarm provider reads planned for v0.6.

HTTPS

Section titled “HTTPS”

These platforms obtain certificates through their own Traefik. ReverseDock’s automatic certificates are since v0.3; until then, routes from these labels need a certificate you provide, or tls: off on a plain listener as above.

Section titled “Related”