Traefik not running after fresh install - `read /etc/traefik/traefik.yml: is a directory`

[martijnvdbrug]

To Reproduce

Traefik doesn't start on GCP Compute Engine with Ubuntu 24: read /etc/traefik/traefik.yml: is a directory

This seems to be a duplicate of #1586, but that seems to be closed already. I have added GCE machine details in this comment.

Update

On a new instance, with SSD instead of persistent disk, Traefik is installed and running successfully. I see that this commit was a fix for this issue, but I can imagine that waiting for 4 seconds can cause race conditions. (Slower CPU, slower disk etc)

Output of the installation script:

curl -sSL https://dokploy.com/install.sh | sudo sh
# Executing docker install script, commit: 7d96bd3c5235ab2121bcb855dd7b3f3f37128ed4
+ sh -c apt-get -qq update >/dev/null
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get -y -qq install ca-certificates curl >/dev/null
+ sh -c install -m 0755 -d /etc/apt/keyrings
+ sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" -o /etc/apt/keyrings/docker.asc
+ sh -c chmod a+r /etc/apt/keyrings/docker.asc
+ sh -c echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu noble stable" > /etc/apt/sources.list.d/docker.list
+ sh -c apt-get -qq update >/dev/null
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get -y -qq install docker-ce docker-ce-cli containerd.io docker-compose-plugin docker-ce-rootless-extras docker-buildx-plugin docker-model-plugin >/dev/null
Scanning processes...                                                                                          
Scanning linux images...                                                                                       
+ sh -c docker version
Client: Docker Engine - Community
 Version:           29.0.3
 API version:       1.52
 Go version:        go1.25.4
 Git commit:        511dad6
 Built:             Thu Nov 20 16:44:19 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          29.0.3
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.4
  Git commit:       1fa8a31
  Built:            Thu Nov 20 16:44:19 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.1.5
  GitCommit:        fcd43222d6b07379a4be9786bda52438f0dd16a1
 runc:
  Version:          1.3.3
  GitCommit:        v1.3.3-0-gd842d771
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

================================================================================

To run Docker as a non-privileged user, consider setting up the
Docker daemon in rootless mode for your user:

    dockerd-rootless-setuptool.sh install

Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.


To run the Docker daemon as a fully privileged service, but granting non-root
users access, refer to https://docs.docker.com/go/daemon-access/

WARNING: Access to the remote API on a privileged Docker daemon is equivalent
         to root access on the host. Refer to the 'Docker daemon attack surface'
         documentation for details: https://docs.docker.com/go/attack-surface/

================================================================================

Using advertise address: 10.164.0.7
Swarm initialized: current node (ot5blh66d0nb8tzyisbk9mqec) is now a manager.

To add a worker to this swarm, run the following command:

    docker swarm join --token SWMTKN-1-3jvvvjtm51lzge9utwk6iesv8kedauwnqdx9by6voa4uxsstbj-9wynlfjvnjjb0texfj923k50s 10.164.0.7:2377

To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
Swarm initialized
ks9hie7pf32gdl7adx3iel20h
Network created

0kcg76g35nds00jtrd9o0arlb
overall progress: 1 out of 1 tasks 
1/1: running   [==================================================>] 
verify: Service 0kcg76g35nds00jtrd9o0arlb converged 

qsnyzsse0kaydxp41v8cj5bqd
overall progress: 1 out of 1 tasks 
1/1: running   [==================================================>] 
verify: Service qsnyzsse0kaydxp41v8cj5bqd converged 

zp45krmm55ebvi3oloiz7mwys
overall progress: 1 out of 1 tasks 
1/1: running   [==================================================>] 
verify: Service zp45krmm55ebvi3oloiz7mwys converged 
Unable to find image 'traefik:v3.6.1' locally
v3.6.1: Pulling from library/traefik
bc116d93e45b: Pull complete 
43a5be716dde: Pull complete 
e12cf03b5b74: Pull complete 
2d35ebdb57d9: Pull complete 
Digest: sha256:fd5932c796f7e2db9fd6bff485ef693d53797f0ee8ad03dc68aa424ea6f21958
Status: Downloaded newer image for traefik:v3.6.1
7352e33fc75025e84a282ad43ace6304888b3ccb6476b478503c1d3eb8723c6f

Congratulations, Dokploy is installed!
Wait 15 seconds for the server to start
Please go to http://34.12.182.213:3000

Current vs. Expected behavior

Expected Traefik to start normally on a clean installation on a supported OS.

Provide environment information

Google Cloud Compute Engine: e2-small (2 vCPUs, 2 GB Memory), Standard persistent disk
ubuntu-2404-noble-amd64-v20251121
X86_64
Dokploy version v0.25.10

Which area(s) are affected? (Select all that apply)

Traefik

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

[Siumauricio]

Thanks for the repro; I was finally able to reproduce it. Apparently, this happens on very slow machines, causing a race condition. What I did was create the files well before initializing the Dokploy application, which is responsible for creating them correctly before the Dokploy app starts.