-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traefik does not attach itself to provided docker networks. #10656
Comments
This would be great to see, but would need write access to the docker config - making things like wollomatic/socket-proxy more complex (hopefully not impossible). |
Hello @chrisbecke, Thanks for reaching out. A container cannot be attached to a network after its creation without being restarted. I recommend you take a look in the community forum. It is pretty active, so you might find that your question has already been answered there. If not, you can ask and get help from other community members pretty quickly. |
See now heres the thing. There are a lot of things about containers that do require a restart. Networks however are, ironically, one of the resources that can be added on the fly See "re-attaching" networks to running containers is called out as problematic, so "add, remove, add" will need to be avoided. |
Hello @chrisbecke, I re-opened the issue to make some checks according to your previous message. |
Welcome!
What did you do?
What did you see instead?
I expected to see the output from whoami in the 3rd step.
It seems Traefik is not using the provided docker network via the
traefik.docker.network
label to attach itself.What version of Traefik are you using?
v3.0
What is your environment & configuration?
compose.yaml
If applicable, please paste the log output in DEBUG level
The text was updated successfully, but these errors were encountered: