-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Problem installing or searching pack, temporary failure in name resolution #216
Comments
By default bridge networks dont forward to the outside world and need to have additional parameters set on the host for this to work correctly. |
@minsis I tried it, and indeed also tried changing the type of network, but the problem is still the same. |
@JustDevZero We also faced some of these issues (not with StackStorm) when ipv6 was enabled and ultimately disabled it. Do you also have ipv6 enabled? |
I'll check it as soon as I'm at my office hours, but I think you're maybe
having a point on the ipv6, AFAIK we have ipv6 disabled on whole network.
El jue., 4 mar. 2021 22:34, Dennis Whitney <[email protected]>
escribió:
… @JustDevZero <https://github.com/JustDevZero> We also faced some of these
issues (not with StackStorm) when ipv6 was enabled and ultimately disabled
it. Do you also have ipv6 enabled?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#216 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABKFV33A6MSV3UXJOM4ZJTTB74GVANCNFSM4YHOXTIQ>
.
|
@JustDevZero The network itself can have ipv6 disabled as a whole but that doesn't prevent localhost from having it enabled. Every device has its own link local ipv6 address when it comes up. |
It looks that it's ipv6 fault then, host have ipv6 disabled but somehow docker it's still trying to get ipv6 not 4. So... I guess it's matter of dealing with docker config, maybe? |
Hi, Every action in python 3 that need to resolve a DNS happens the same problem: @JustDevZero have you manager to find out what was the root cause of this issue? Versions
|
This fixed the issue for me:
|
By default ipv4 forwarding is not enabled. This is mostly where the issue is with getting traffic to leave the container. Add |
Describe the problem
A clear and concise description of what the problem is.
Versions
To Reproduce
If necessary, please specify steps to reproduce the behavior.
Login to st2client with:
docker-compose exec st2client bash
And then try to search or install.
It will fail with:
If try to do some curl... from st2api container:
Modifying resolve.conf for adding 1.1.1.1 after docker resolution improves the thing but still.
From s2client container on the other hand it's inmediate.
For some reason, s2api container it's taking more time to resolv... But even with that it's no reason for getting a Temporary failure in name resolution.
Am i installing them wrong?
The text was updated successfully, but these errors were encountered: