[Fuego] [LTSI-dev] Fuego installation errors on Ubuntu 16.04 LTS (64-bit)

dhinakar k dhinakar.k at gmail.com
Fri Mar 3 05:37:39 UTC 2017


Hi Bird,

Thank you very much for your prompt support.
I investigated again and check with our company linux administrator.
He confirmed that the dns namerserver 8.8.8.8 is blocked in our company.
Hence I replaced the nameserver ip addresses in the /etc/resolv.conf with
the ones he gave me.
Earlier the nameserver was set to 127.0.1.1, it did not matter for my
ubuntu 16.04 host but docker was not able to resolve.
The replacement worked like charm and I am able to go through with the
installation.

Thanks a lot for your time and support.

Regards,
Dhinakar

On Fri, Mar 3, 2017 at 2:16 AM, Bird, Timothy <Tim.Bird at sony.com> wrote:

>
>
> > -----Original Message-----
> > From: dhinakar k on Thursday, March 02, 2017 5:18 AM
> > I think have trouble shooted the issue.
> > It seems to be a dns issue when /etc/resolv.conf has nameserver
> 127.0.1.1 in
> > it.
> >
> >
> > I tried adding DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4" to the
> > /etc/default/docker file but no use.
> >
> Apparently, in some configurations, DOCKER_OPTS is not used.
>
> See https://github.com/docker/docker/issues/9889#issuecomment-109766580
>
> I'm using Ubuntu 14.04, and the top of my /etc/default/docker says:
>
> #
> # THIS FILE DOES NOT APPLY TO SYSTEMD
> #
> #   Please see the documentation for "systemd drop-ins":
> #   https://docs.docker.com/engine/admin/systemd/
>
> I'm guessing that since you're using Ubuntu 16.04, you are using
> systemd by default, and this would apply to your case.
>
> Another thing to check is that your host has access to 8.8.8.8 from
> inside your network.  I believe earlier you said that you are not
> behind a proxy.  You might try temporarily replacing your nameserver
> on your host (e.g. with 8.8.8.8), and pinging google.com, just to
> double-check this.
>
> It appears that the --dns option does not apply during 'docker build'
> anyway, and that's where you're having the problem.
>
> However, I found this issue:
> https://github.com/docker/docker/issues/5779#issuecomment-59946467
>
> gdm85 says it should be possible to edit /etc/resolv.conf during the build
> to point to a custom DNS (8.8.8.8 should work).  After the operations
> that require this (the Jessie package updates), then the default
> /etc/resolv.conf
> should be restored.
>
> I can't duplicate the problem here, but could you try adding some lines
> like
> the following to your Dockerfile, and let me know what the results are?
>
> Here's a patch to try:
> diff --git a/Dockerfile b/Dockerfile
> index f9f2fb7..e54d391 100644
> --- a/Dockerfile
> +++ b/Dockerfile
> @@ -20,6 +20,8 @@ ENV URL_PREFIX /fuego
>  # ============================================================
> ==================
>
>  WORKDIR /fuego-install
> +COPY /etc/resolv.conf /etc/resolv.conf.save
> +RUN echo nameserver 8.8.8.8 > /etc/resolv.conf
>  RUN dpkg --add-architecture i386
>  RUN echo deb http://ftp.us.debian.org/debian jessie main non-free >>
> /etc/apt/sources.list
>  RUN if [ -n "$HTTP_PROXY" ]; then echo 'Acquire::http::proxy
> "'$HTTP_PROXY'";' > /etc/apt/apt.conf.d/80proxy; fi
> @@ -124,4 +126,5 @@ WORKDIR /home/jenkins
>  COPY fuego-scripts /
>  COPY fuego-scripts/fuego-start-cmd.sh /etc/
>  CMD /etc/fuego-start-cmd.sh
> +COPY /etc/resolv.conf.save /etc/resolv.conf
> ----
>
> It's not entirely clear to me, if this solves the install dns issues, that
> it's appropriate to restore
> the saved /etc/resolv.conf.  It seems like there would be problems at
> runtime in the container.
> However, docker does some pretty mystical stuff with resolv.conf inside
> containers.
> I'm not really sure what will happen.
>
> Please let me know what you find out.
>   -- Tim
>
> > I get the following...
> >
> > xxx at localhost:~/fuego$ docker run --rm debian:jessie ping -c 5
> google.com
> > <http://google.com>
> > ping: unknown host
> >
> > but it works with ip address 8.8.8.8 (as given below)
> >
> > xxx at localhost:~/fuego$ docker run --rm debian:jessie ping -c 5 8.8.8.8
> > PING 8.8.8.8 (8.8.8.8): 56 data bytes
> > 64 bytes from 8.8.8.8 <http://8.8.8.8> : icmp_seq=0 ttl=55 time=10.584
> ms
> > 64 bytes from 8.8.8.8 <http://8.8.8.8> : icmp_seq=1 ttl=55 time=10.137
> ms
> > 64 bytes from 8.8.8.8 <http://8.8.8.8> : icmp_seq=2 ttl=55 time=10.471
> ms
> > 64 bytes from 8.8.8.8 <http://8.8.8.8> : icmp_seq=3 ttl=55 time=10.316
> ms
> > 64 bytes from 8.8.8.8 <http://8.8.8.8> : icmp_seq=4 ttl=55 time=10.261
> ms
> > --- 8.8.8.8 ping statistics ---
> > 5 packets transmitted, 5 packets received, 0% packet loss
> > round-trip min/avg/max/stddev = 10.137/10.354/10.584/0.157 ms
> >
> >
> > This thread -> https://github.com/docker/docker/issues/541 discusses
> about
> > this issue in detail. I want to know what is the current best resolution
> > adopted for this issue. Please let me know.
> >
> >
> > Regards,
> >
> > Dhinakar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20170303/3e3893a3/attachment-0001.html>


More information about the Fuego mailing list