Hello guys,
when stopping the Traefik Docker container I am getting those
2025-06-13T17:50:28+02:00 ERR error="accept tcp [::]:80: use of closed network connection" entryPointName=web
2025-06-13T17:50:28+02:00 ERR error="close tcp [::]:80: use of closed network connection" entryPointName=web
errors. I found many threads saying just ignore them and start the container again, which is working, but I couldnt find a solution about how to lose / avoid theses errors?
Because when I reboot my Debian system, all my Docker containers come back up thanks to --restart unless-stopped , but Traefik is not.
Due to that closed network connection error from shutting down it stays down, and this is very annoying. Booting up everything without the very much needed Traefik border router.
time="2025-06-14T16:46:04.955346290+02:00" level=error msg="failed to start container"
container=ed8aeb981d6aac6fbb933905faaf5d7f2c049aec03562709f2a78451b4d9d40d
error="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
\"/path/tailscale/run/tailscaled.sock\" to rootfs at \"/var/run/tailscale/tailscaled.sock\": create
mountpoint for /var/run/tailscale/tailscaled.sock mount: cannot create subdirectories in
\"/var/lib/docker/overlay2/bb3ac3308587564d2e5473524bc92869600e04dd99c6e9ba2429d3db9
9e70d7a/merged/run/tailscale/tailscaled.sock\": 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"
This is because Im using Tailscale and it's TLS certs with Traefik. First I need to start the Tailscale container and do a bind mount affecting tailscaled.sock and then Ill have to bind mount that socket to Traefik. Looks to me when everything is rebooting and restarting at the same time things are not happening in the right order.
How do I change this? I would need to add a 30s delay to the Traefik docker compose at startup, and couldn't figure this out. (Tried google but didn't find a working solution)
I cannot put the two containers in one compose stack and do a "depends on"-setting because the containers are in different Docker networks. Tailscale is running in network mode host, Traefik is using a separate bridge network.
The depends_on directive only works with services in the same docker compose project.
And I cannot put Tailscale and Traefik in the same compose project because of docker networking: Tailscale should run in the host network, Traefik in a separate bridge network.
This sums up my (beginner‘s) docker knowledge and what I was able to look up and try out using google.
I could run all containers in the host network (Tailscale, Traefik, every proxied service), but that would be against Docker‘s networking concepts and principles I guess??
I thought I could not and I failed before... BUT as it turns out: I can.
So docker-wise, Ive made it happen: created a compose project which starts up Tailscale, then waits for it to become 'healthy' then spins up Traefik. Works like a charm.
time="2025-06-16T05:31:37.779063771+02:00" level=error msg="failed to start
container" container=841eba error="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
\"/mypath/tailscale/run/tailscaled.sock\" to rootfs at
\"/var/run/tailscale/tailscaled.sock\": create mountpoint for
/var/run/tailscale/tailscaled.sock mount: cannot create subdirectories in
\"/var/lib/docker/overlay2/da30a/merged/run/tailscale/tailscaled.sock\":
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"
Any further ideas?
@bluepuma77 Thank you very much for the help on docker / docker compose. Your questions were pointing me into the right direction and Ive learned a thing or two
It's not really a docker problem, either. I'm pretty sure it's a tailscale problem. I believe the problem is that Compose is creating the bind to /mypath/tailscale/run/tailscaled.sock for the traefik container before starting the tailscale container, while the tailscale container is actually creating that socket. Can you bind /mypath/tailscale/run, rather than just the socket file? Or if that exposes too much to your traefik container, can you specify a different path for the socket to Tailscale, and then bind the directory that will contain that to both containers.
