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
Docker resolver: hostmachine 127.0.0.1 usage broken #38512
Comments
CharlieR-o-o-t
pushed a commit
to CharlieR-o-o-t/libnetwork
that referenced
this issue
Jan 8, 2019
Control param checkLoopback depending on sb.config.dnsList * if dnsList contains 127.0.0.1 - HostLoopback will be set to false. Container net namespace will be used to access loopback dns . Fix to moby/moby#38512
Proposed solution : |
CharlieR-o-o-t
pushed a commit
to CharlieR-o-o-t/libnetwork
that referenced
this issue
Feb 13, 2019
Control param checkLoopback depending on sb.config.dnsList * if dnsList contains 127.0.0.1 - HostLoopback will be set to false. Container net namespace will be used to access loopback dns . Fix to moby/moby#38512 Signed-off-by: Siarhei Rasiukevich <raskintech@gmail.com>
CharlieR-o-o-t
pushed a commit
to CharlieR-o-o-t/libnetwork
that referenced
this issue
Feb 13, 2019
Control param checkLoopback depending on sb.config.dnsList * if dnsList contains 127.0.0.1 - HostLoopback will be set to false. Container net namespace will be used to access loopback dns . Fix to moby/moby#38512 Signed-off-by: Siarhei Rasiukevich <raskintech@gmail.com>
CharlieR-o-o-t
pushed a commit
to CharlieR-o-o-t/libnetwork
that referenced
this issue
Feb 13, 2019
Control param checkLoopback depending on sb.config.dnsList * if dnsList contains 127.0.0.1 - HostLoopback will be set to false. Container net namespace will be used to access loopback dns . Fix to moby/moby#38512 Signed-off-by: Siarhei Rasiukevich <raskintech@gmail.com>
CharlieR-o-o-t
pushed a commit
to CharlieR-o-o-t/libnetwork
that referenced
this issue
Feb 13, 2019
Control param checkLoopback depending on sb.config.dnsList * if dnsList contains 127.0.0.1 - HostLoopback will be set to false. Container net namespace will be used to access loopback dns . Fix to moby/moby#38512 Signed-off-by: Siarhei Rasiukevich <raskintech@gmail.com>
CharlieR-o-o-t
pushed a commit
to CharlieR-o-o-t/libnetwork
that referenced
this issue
Feb 13, 2019
Control param checkLoopback depending on sb.config.dnsList * if dnsList contains 127.0.0.1 - HostLoopback will be set to false. Container net namespace will be used to access loopback dns . Fix to moby/moby#38512 Signed-off-by: Siarhei Rasiukevich <raskintech@gmail.com>
CharlieR-o-o-t
pushed a commit
to CharlieR-o-o-t/libnetwork
that referenced
this issue
Feb 13, 2019
Control param checkLoopback depending on sb.config.dnsList * if dnsList contains 127.0.0.1 - HostLoopback will be set to false. Container net namespace will be used to access loopback dns . Fix to moby/moby#38512 Signed-off-by: Siarhei Rasiukevich <raskintech@gmail.com>
PR : moby/libnetwork#2338 |
I believe this has been fixed as of v23.0.2, v24.0.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Hostmachine 127.0.0.1 cannot be used as resolver if DnsSearch/DnsOpts in use - container tries to reach hostmachine 127.0.0.1 with own namespace.
Need workaround on RP
Container resolv.conf looks like this:
Hostmachine resolv.conf
Here extConnect should be called, but HostLoopback is empty field
components/engine/vendor/github.com/docker/libnetwork/resolver.go:442
Steps to reproduce the issue:
Describe the results you received:
Docker attempts to reach hostmachine 127.0.0.1 at container namespace
Describe the results you expected:
Docker will use global net namespace to reach HostLoopback
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:affects any version
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: