You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I've had some issues with an alpine:3.9 based container. After extensive digging ( see fluxcd/flux#1980 ) I think this is due to alpine's issues with name resolution ( a quick look into the issues of the docker-alpine project shows that I'm not alone in that). At this point it's unclear what's happening, I've tried to upgrade CoreDNS to 1.5.0 but the issue it's still there.
It has something to do with the searches into the declared domain (this is the file /etc/resolv.conf):
Other base images like Busybox or Debian seems not to be affected by this
Steps to reproduce
in my case:
$ kubectl run -i --tty --image-pull-policy=Always --image alpine:3.9 dns-tests --restart=Never --rm /bin/sh
If you don't see a command prompt, try pressing enter.
/ # ping -c 1 gitlab.com
ping: bad address 'gitlab.com'
/ # ping -c 1 pippo.it
ping: bad address 'pippo.it'
# nslookup gitlab.com
nslookup: can't resolve '(null)': Name does not resolve
nslookup: can't resolve 'gitlab.com': Name does not resolve
but explictly making the resolution absolute does the trick:
/ # nslookup gitlab.com.
nslookup: can't resolve '(null)': Name does not resolve
Name: gitlab.com.
Address 1: 35.231.145.151 151.145.231.35.bc.googleusercontent.com
/ # ping -c 1 gitlab.com.
PING gitlab.com. (35.231.145.151): 56 data bytes
64 bytes from 35.231.145.151: seq=0 ttl=42 time=103.690 ms
--- gitlab.com. ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 103.690/103.690/103.690 ms
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Issue description
Hello,
I've had some issues with an alpine:3.9 based container. After extensive digging ( see fluxcd/flux#1980 ) I think this is due to alpine's issues with name resolution ( a quick look into the issues of the docker-alpine project shows that I'm not alone in that). At this point it's unclear what's happening, I've tried to upgrade CoreDNS to 1.5.0 but the issue it's still there.
It has something to do with the searches into the declared domain (this is the file
/etc/resolv.conf
):Other base images like Busybox or Debian seems not to be affected by this
Steps to reproduce
in my case:
but explictly making the resolution absolute does the trick:
Technical details
"x86_64-linux"
Linux 5.0.10, NixOS, 19.03pre-git (Koi)
yes
yes
nix-env (Nix) 2.2.2
"nixos-19.03.172477.8838032e905"
/nix/var/nix/profiles/per-user/root/channels/nixos
K8s is installed from unstable:
The text was updated successfully, but these errors were encountered: