Hi, On Tue, 8 Mar 2016 22:58:01 -0600 Clayton Coleman <[email protected]> wrote: > There is a discussion upstream about this, and ensuring that names for > pods can be resolved. In the short term it is not possible to resolve > the pod hostname to itself.
I see. I wait until this problem is resolved at upstream and appears in OpenShift. > Can the worker run without being able to > resolve the hostname? Cannot. The worker is going to resolve the hostname for interface's IP address. This is not configurable setting (maybe, I am asking Hadoop guys now). I found a workaround: 1) loosen SCC to get root privilege in container. 2) modify the worker's /etc/hosts at deploying container from "172.17.0.10 worker-1-f6kr5" to "172.17.0.10 worker". 3) then, the worker uses own hostname as "worker" (service name), it works well. But I am happy if /etc/hosts entry is configurable, so it will not require to loosen SCC and craft Dockerfile. -- HIGUCHI Daisuke <[email protected]> _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
