It looks like this project was started prior to the release of docker's host networking feature.
The use of dnsmasq here is for reverse DNS (since the container and host don't share the same hostname), right? Now that one can do docker run --net host -P .... to make the container and host share the same network interface, it's no longer necessary to have a custom reverse DNS solution. This approach does work: I've gotten Spark and HDFS running in docker 1.1.2 w/out custom DNS. You might consider removing the dnsmasq dependency or perhaps clarifying to users which docker versions require custom DNS.
Thanks for posting these scripts, though! They've had significant educational value 8)
It looks like this project was started prior to the release of docker's host networking feature.
The use of dnsmasq here is for reverse DNS (since the container and host don't share the same hostname), right? Now that one can do
docker run --net host -P ....to make the container and host share the same network interface, it's no longer necessary to have a custom reverse DNS solution. This approach does work: I've gotten Spark and HDFS running in docker 1.1.2 w/out custom DNS. You might consider removing the dnsmasq dependency or perhaps clarifying to users which docker versions require custom DNS.Thanks for posting these scripts, though! They've had significant educational value 8)