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
IPV6 :: bound instead of V4 0.0.0.0 #47793
Comments
Hi @NoRePercussions - I've had a quick play, but haven't been able to reproduce the problem. You're using a very old version of the docker client (19.03.9, from 2020). Perhaps you also have an old version of |
Did using a current version of |
I can't reproduce it on a fresh bullseye 11.9 machine, and will further try on a bookworm 12.5 machine, so I suspect you are right. Thank you for your help! |
Ok, great! Thank you for the update. |
Description
I am on Debian 12.5.
I run
docker run 11f -p 0.0.0.0:8080:8080
, and see the proxy bind the following socket:I do not see this behavior when binding a socket with Python:
This causes a problem with the docker proxy's default interfaces, as the proxy tries to bind
0.0.0.0
(which is changed to::
) and then tries to bind::
, which fails because the first bind already includes it:Additionally, the
::
bind accepts connections from ipv4, which is unexpected since I havenet.ipv6.bindipv6only = 1
.Reproduce
Proxy a container's ports with `docker run -p 0.0.0.0:8080:8080 mycontainer
Expected behavior
When binding
0.0.0.0
, I don't expect::
to be bound, and vice versa. Additionally, I expect binding default interfaces to succeed.docker version
docker info
Additional Info
No response
The text was updated successfully, but these errors were encountered: