Where Does Dokploy Store Data and Config?
Dokploy keeps its config under /etc/dokploy on Linux, with Postgres and app data in named Docker volumes beside it.
Last updated
Dokploy is a Linux and Docker creature, so everything starts at /etc/dokploy. The installer creates that directory and bind-mounts it into its services. Traefik config, dynamic middlewares and per-project files all branch from there.
Databases live outside that tree in named volumes. Postgres holds the control plane and each app can add its own mounts under a files folder referenced from compose. For a full move, you need both halves: the /etc/dokploy tree and the volume contents. One without the other restores an empty shell.
Where Dokploy stores this, by platform
/etc/dokploy
Installer-created root holding traefik.yml, the dynamic middlewares folder and project data. Dokploy's documented backup zips this tree with Postgres. Per-app file mounts appear as files folders referenced from compose, with the host prefix varying by version.
/var/lib/docker/volumes/dokploy-postgres/_data
On-host storage for Dokploy's named volumes including dokploy-postgres. Inspect names with docker volume ls first. Back up the Postgres volume alongside /etc/dokploy; either half alone is not a working restore.
Frequently asked questions
What do I back up to move Dokploy to a new server?
Back up /etc/dokploy in full plus a dump of the dokploy-postgres volume. Dokploy's own backup zips exactly that pair to S3. Restoring replaces /etc/dokploy wholesale, so snapshot before overwriting a live host.
Which Docker volumes belong to Dokploy?
Run docker volume ls and look for dokploy-postgres plus a volume literally called dokploy. On disk they sit under /var/lib/docker/volumes/<name>/_data. The Postgres volume is the database, the dokploy volume maps to /root/.docker in the container.
Where is the Dokploy Traefik config?
Open /etc/dokploy/traefik/traefik.yml and the dynamic folder next to it. Middlewares and routing rules live there. The installer creates /etc/dokploy with wide permissions, so tighten them after setup on shared hosts.
Notice an outdated path? Let us know.