-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
To Reproduce
Download Dokploy from official method (curl -sSL https://dokploy.com/install.sh | sh)
Run sudo docker ps -a
Run sudo docker logs dokploy-traefik
Current vs. Expected behavior
Due to the bug, traefik never starts and the container keeps restarting in a loop.
Provide environment information
Raspberry Pi 3
Linux raspberrypi 6.12.25+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
Dokploy version: 0.22.7
Which area(s) are affected? (Select all that apply)
Installation, Traefik, Docker
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
The problem is in the /etc/dokploy/traefik/traefik.yml path. traefik.yml is being interpreted as a directory, not a file. I tried stopping the dokploy-traefik container, delete the directory and create the traefik.yml file, but when starting the container again I get this error:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/etc/dokploy/traefik/traefik.yml" to rootfs at "/etc/traefik/traefik.yml": mount src=/etc/dokploy/traefik/traefik.yml, dst=/etc/traefik/traefik.yml, dstFd=/proc/thread-self/fd/8, flags=0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Error: failed to start containers: 45621969a19e
Will you send a PR to fix it?
No