-
-
Notifications
You must be signed in to change notification settings - Fork 110
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
EAI_AGAIN error on microk8s #276
Labels
Comments
I did look at that one before I opened this. I'm not sure if it is related since I do appear to be able to run an nslookup from the container. My CoreDNS config looks very similar as well.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃悰 Bug Report
I am unable to cleanly start the
:stable
version of the container on my 4 node microk8s cluster(arm64v8)To Reproduce
Steps to reproduce the behavior:
Expected behavior
expecting the container to start up cleanly. What I find odd here is the
EAI_AGAIN
error seems to be related to DNS, however the container does appear to successfully do a lookup when I exec into itlog output
The text was updated successfully, but these errors were encountered: