[Hawkular-dev] Docker build on a VM

[John Mazzitelli]

I saw the same problems. One thing I don't understand is why my host's resolve.conf isn't good enough?

https://docs.docker.com/engine/userguide/networking/default_network/configure-dns/

"Regarding DNS settings, in the absence of the --dns=IP_ADDRESS..., --dns-search=DOMAIN..., or --dns-opt=OPTION... options, Docker makes each container’s /etc/resolv.conf look like the /etc/resolv.conf of the host machine (where the docker daemon runs). When creating the container’s /etc/resolv.conf, the daemon filters out all localhost IP address nameserver entries from the host’s original file."

I'm not having any connectivity issues from my host machine - so why does the docker container have problems if it is using the same /etc/resolve.conf?

It's all magic to me.

----- Original Message -----
> 
> I was stumped for quite a while about why I couldn't get a docker build to
> run on my VM. The symptom is that the docker build can not reach the outside
> world, and therefore can't pull in what it needs. This happens even though
> the VM itself has no connectivity issues. Note, I assume this is a VM thing
> because it happened to both mazz and myself, using Virtual Box fedora vms,
> but it may not be limited to VMs. I finally stumbled on a stack overflow
> entry that solved the issue [1].
> 
> Basically, you need to tell docker about your DNS servers, and also Google's
> DNS server 8.8.8.8. Your mileage may vary, perhaps you'll only need a subset
> of of servers, but hopefully this helps you out, because it was a pita.
> 
> [1]
> http://stackoverflow.com/questions/25130536/dockerfile-docker-build-cant-download-packages-centos-yum-debian-ubuntu-ap
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>