kubedns 1.13.0 failed to start on v1.6.0-alpha.3 (s390x) about dns HOT 5 CLOSED

Can you post the container logs too?

from dns.

like the problem is from k8s-dns-sidecar-s390x:1.13.0 image, need to add nobody group into /etc/group file, in short, append below line to file /etc/group of image k8s-dns-sidecar-s390x:1.13.0

nobody:x:101:

Error message from the container:
Error response from daemon: {"message":"linux spec user: unable to find group nobody: no matching entries in group file"}

from dns.

please open a PR to fix

from dns.

Hello XiLongZheng

Recently I tested the new version of kube dns 1.14.1 and there I did not see any problem for all the images viz. dns, dnsmasq and sidecar so can you test with the latest version. I came across this specific problem for "exechealthz" available for s390x. So can you confirm this issue is with sidecar or exechealthz?

from dns.

We just got a chance to try kube dns 1.14.1 with Kubernetes 1.6.1 on s390x, worked perfect now. Thanks for the great help everyone provided! Closing this now.

from dns.