-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
dns problem in apline based docker image #442
Comments
I guess this problem has nothing to do with kind, it is probably due to the problem of and you can try to use |
/triage needs-information |
should I close this issue for a alpine related issue? |
right. please see: gliderlabs/docker-alpine#476 |
OK, thanks @tao12345666333 |
You may need kubernetes/kubernetes@4274c42 if you're using go in your Alpine image. |
Or rather: an etc/nsswitch.conf entry. Your Debian image most likely has one. |
kubernetes/kubernetes#69238 and kubernetes/kubernetes#69195 have some more discussion. This issue is generic to alpine (non glibc) images with go binaries |
What happened:
I've had a dns problem, the pod container can not resolve the external network dns like
github.com
.There's a similar issue in kubernetes repository kubernetes/kubernetes#64924, but I'm not sure the problem is the same with it.
In my case, it only happened on
alpine
based image, it works onDebian
based image in kind k8s cluster, but it works on docker desktop k8s cluster, so I'm consufed.What you expected to happen: I think it should resolve the external dns correctly
How to reproduce it (as minimally and precisely as possible):
you can use this Dockerfile to build a image or use
weihanli/accountingapp:latest
for alpine based image to have a testAnything else we need to know?:
Environment:
kind version: (use
kind version
): 0.2.1Kubernetes version: (use
kubectl version
):Docker version: (use
docker info
):WARNING: No swap limit support
OS (e.g. from
/etc/os-release
):The text was updated successfully, but these errors were encountered: