So, it was important for me to add the corporate DNS servers from the HOST machine in order to get the VM also to work. We now have GitHub Enterprise and CoreOS Enterprise Docker Registry in the mix. Permanent VM Solution - UPDATE JULY 2, 2015 Thanks to and others who helped in the IRC channel! Step 2 : RUN yum install -y curl yum upgrade -y yum update -y yum clean all Removing intermediate container 49bc6e233e4c Step 1 : MAINTAINER Running in 49bc6e233e4c Sending build context to Docker daemon 7.168 kB I just took those 2 IP addresses and placed under the Ubuntu's docker daemon configuration: ~ $ cat /etc/default/docker My host might be dropping the packets to the Google's IP address 8.8.8.8 while building. My MAC OS X, host OS, had a different DNS configured on my /etc/nf: ~ (mac) $ cat /etc/nf Start the Docker daemon with the -dns switch to point to your private DNS server, just like your host OS is configured. Even if the docker container can ping 8.8.8.8, the build still needs to have access to the same private DNS server behind your firewall or Data Center.
This problem occurs in an environment that has a private DNS server, or the network blocks the Google's DNS servers. The build works just fine at a regular Internet connection at home. Talking to some developers at the problem was clear to everyone: DNS and the environment.
So, most users on mentioned that it might be a problem with the DNS configuration. Step 2 : RUN yum install -y curl yum upgrade -y yum update -y yum clean allĬouldn't resolve host '
Users have reported that it might be problems with DNS configuration, others and the configuration has the Google's DNS servers commented out. I know that we can run a container with -dns, but this is during the build time. PROBLEM: Any build, with a Dockerfile depending on centos, ubuntu or debian fails to build.ĮNVIRONMENT: I have a Mac OS X, running VMWare with a guest Ubuntu 14.04, running Docker: ~ $ sudo docker versionīEHAVIOR: Using "docker build" fails to download packages.
0 kommentar(er)
