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

dhinakar k dhinakar.k at gmail.com
Thu Mar 2 13:18:26 UTC 2017


Hi Bird,

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.

I get the following...

xxx at localhost:~/fuego$ docker run --rm debian:jessie ping -c 5 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: icmp_seq=0 ttl=55 time=10.584 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=10.137 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=10.471 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=10.316 ms
64 bytes from 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



On Thu, Mar 2, 2017 at 3:54 PM, dhinakar k <dhinakar.k at gmail.com> wrote:

> Hi Bird,
>
> Thank you very much for your prompt response.
>
> I am from India and I modified the Dockerfile to pull from
> ftp.sg.debian.org as Singapore is quite close to me. The connection to
> internet is direct, no proxy server used. I get the following errors pasted
> below again. Actually there is no 'InRelease' in debian.org jessie but
> still i see this -> *http://ftp.sg.debian.org <http://ftp.sg.debian.org>
> jessie InRelease* in the err log. Can you please help me point to the
> exact issue?
>
> I have started docker daemon (sudo docker daemon) on another terminal
> before triggering the installation of fuego (via install.sh script). Is
> that how it is usually done?
>
> Also my system is 64-bit, this -> *Step 8 : RUN dpkg --add-architecture
> i386* is needed in Dockerfile?
>
> *Fuego Installation error log*
> XXXX:~/fuego$ ./install.sh
> Sending build context to Docker daemon 105.1 MB
> Step 1 : FROM debian:jessie
>  ---> 978d85d02b87
> Step 2 : MAINTAINER tim.bird at am.sony.com
>  ---> Using cache
>  ---> e1dab8cdbab1
> Step 3 : ARG HTTP_PROXY
>  ---> Using cache
>  ---> 5ef46686acdf
> Step 4 : ENV INST_FUEGO_ENGINE_PATH /home/jenkins
>  ---> Using cache
>  ---> d12194b4c9bd
> Step 5 : ENV INST_FUEGO_FRONTEND_PATH /var/lib/jenkins
>  ---> Using cache
>  ---> c3cff966348a
> Step 6 : ENV URL_PREFIX /fuego
>  ---> Using cache
>  ---> d47cf186937a
> Step 7 : WORKDIR /fuego-install
>  ---> Using cache
>  ---> c2ff647749ac
> Step 8 : RUN dpkg --add-architecture i386
>  ---> Using cache
>  ---> 681941b6cf9d
> Step 9 : RUN echo deb http://ftp.sg.debian.org/debian jessie main
> non-free >> /etc/apt/sources.list
>  ---> Running in 0d8fabd69cdc
>  ---> 604c928c633c
> Removing intermediate container 0d8fabd69cdc
> Step 10 : RUN if [ -n "$HTTP_PROXY" ]; then echo 'Acquire::http::proxy
> "'$HTTP_PROXY'";' > /etc/apt/apt.conf.d/80proxy; fi
>  ---> Running in 896d6dd851cc
>  ---> a93f31ec72be
> Removing intermediate container 896d6dd851cc
> Step 11 : RUN DEBIAN_FRONTEND=noninteractive apt-get update && apt-get -yV
> install apt-utils daemon gcc make python-paramiko python-lxml
> python-simplejson python-matplotlib libtool xmlstarlet autoconf automake
> rsync openjdk-7-jre openjdk-7-jdk iperf netperf netpipe-tcp
> texlive-latex-base sshpass wget git diffstat sudo net-tools vim
> openssh-server curl inotify-tools
>  ---> Running in 40b70ecdb477
> Err http://deb.debian.org jessie InRelease
>
> Err http://deb.debian.org jessie-updates InRelease
>
> Err http://deb.debian.org jessie Release.gpg
>   Could not resolve 'deb.debian.org'
> Err http://ftp.sg.debian.org jessie InRelease
>
> Err http://deb.debian.org jessie-updates Release.gpg
>   Could not resolve 'deb.debian.org'
> Err http://ftp.sg.debian.org jessie Release.gpg
>   Could not resolve 'ftp.sg.debian.org'
> Err http://security.debian.org jessie/updates InRelease
>
> Err http://security.debian.org jessie/updates Release.gpg
>   Could not resolve 'security.debian.org'
> Reading package lists...
> W: Failed to fetch http://deb.debian.org/debian/dists/jessie/InRelease
>
> W: Failed to fetch http://deb.debian.org/debian/
> dists/jessie-updates/InRelease
>
> W: Failed to fetch http://security.debian.org/
> dists/jessie/updates/InRelease
>
> W: Failed to fetch http://ftp.sg.debian.org/debian/dists/jessie/InRelease
>
>
> W: Failed to fetch http://deb.debian.org/debian/dists/jessie/Release.gpg
> Could not resolve 'deb.debian.org'
>
> W: Failed to fetch http://deb.debian.org/debian/
> dists/jessie-updates/Release.gpg  Could not resolve 'deb.debian.org'
>
> W: Failed to fetch http://ftp.sg.debian.org/debian/dists/jessie/Release.
> gpg  Could not resolve 'ftp.sg.debian.org'
>
> W: Failed to fetch http://security.debian.org/
> dists/jessie/updates/Release.gpg  Could not resolve 'security.debian.org'
>
> W: Some index files failed to download. They have been ignored, or old
> ones used instead.
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Package apt-utils is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Package 'apt-utils' has no installation candidate
> E: Unable to locate package daemon
> E: Unable to locate package gcc
> E: Unable to locate package make
> E: Unable to locate package python-paramiko
> E: Unable to locate package python-lxml
> E: Unable to locate package python-simplejson
> E: Unable to locate package python-matplotlib
> E: Unable to locate package libtool
> E: Unable to locate package xmlstarlet
> E: Unable to locate package autoconf
> E: Unable to locate package automake
> E: Unable to locate package rsync
> E: Unable to locate package openjdk-7-jre
> E: Unable to locate package openjdk-7-jdk
> E: Unable to locate package iperf
> E: Unable to locate package netperf
> E: Unable to locate package netpipe-tcp
> E: Unable to locate package texlive-latex-base
> E: Unable to locate package sshpass
> E: Unable to locate package wget
> E: Unable to locate package git
> E: Unable to locate package diffstat
> E: Unable to locate package sudo
> E: Unable to locate package net-tools
> E: Unable to locate package vim
> E: Unable to locate package openssh-server
> E: Unable to locate package curl
> E: Unable to locate package inotify-tools
> The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive apt-get update &&
> apt-get -yV install apt-utils daemon gcc make python-paramiko python-lxml
> python-simplejson python-matplotlib libtool xmlstarlet autoconf automake
> rsync openjdk-7-jre openjdk-7-jdk iperf netperf netpipe-tcp
> texlive-latex-base sshpass wget git diffstat sudo net-tools vim
> openssh-server curl inotify-tools' returned a non-zero code: 100
>
> *Docker Daemon log (for reference)*
> $ sudo docker daemon
> INFO[0000] libcontainerd: new containerd process, pid: 11144
> WARN[0000] containerd: low RLIMIT_NOFILE changing to max  current=1024
> max=65536
> INFO[0001] [graphdriver] using prior storage driver "aufs"
> INFO[0001] Graph migration to content-addressability took 0.00 seconds
> WARN[0001] Your kernel does not support swap memory limit.
> INFO[0001] Loading containers: start.
> .........................INFO[0001] Firewalld running:
> false
> INFO[0001] Default bridge (docker0) is assigned with an IP address
> 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP
> address
>
> INFO[0002] Loading containers: done.
> INFO[0002] Daemon has completed initialization
> INFO[0002] Docker daemon                                 commit=78d1802
> graphdriver=aufs version=1.12.6
> INFO[0002] API listen on /var/run/docker.sock
> WARN[0018] Couldn't run auplink before unmount /var/lib/docker/tmp/docker-aufs-union101757803:
> exec: "auplink": executable file not found in $PATH
> WARN[0018] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> 8c55e8b25d9a0a3b3d0b42ad8a5ac3b2e02591b924a332394ccf843044034ae0-init:
> exec: "auplink": executable file not found in $PATH
> WARN[0018] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> 8c55e8b25d9a0a3b3d0b42ad8a5ac3b2e02591b924a332394ccf843044034ae0: exec:
> "auplink": executable file not found in $PATH
> INFO[0018] No non-localhost DNS nameservers are left in resolv.conf. Using
> default external servers : [nameserver 8.8.8.8 nameserver 8.8.4.4]
> INFO[0018] IPv6 enabled; Adding default IPv6 external servers :
> [nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844]
> WARN[0019] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> 8c55e8b25d9a0a3b3d0b42ad8a5ac3b2e02591b924a332394ccf843044034ae0: exec:
> "auplink": executable file not found in $PATH
> WARN[0019] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> 8c55e8b25d9a0a3b3d0b42ad8a5ac3b2e02591b924a332394ccf843044034ae0: exec:
> "auplink": executable file not found in $PATH
> WARN[0019] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> dd4af5bcbe18a8ad3ef474a177bd6bc1451f69e343d3a5384a933990a972b32e-init:
> exec: "auplink": executable file not found in $PATH
> WARN[0020] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> dd4af5bcbe18a8ad3ef474a177bd6bc1451f69e343d3a5384a933990a972b32e: exec:
> "auplink": executable file not found in $PATH
> INFO[0020] No non-localhost DNS nameservers are left in resolv.conf. Using
> default external servers : [nameserver 8.8.8.8 nameserver 8.8.4.4]
> INFO[0020] IPv6 enabled; Adding default IPv6 external servers :
> [nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844]
> WARN[0020] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> dd4af5bcbe18a8ad3ef474a177bd6bc1451f69e343d3a5384a933990a972b32e: exec:
> "auplink": executable file not found in $PATH
> INFO[0021] Layer sha256:86635e20f9316efb0dca0351690b1a
> f86dcd0348154d53472ddfa132c83e9064 cleaned up
> WARN[0021] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> dd4af5bcbe18a8ad3ef474a177bd6bc1451f69e343d3a5384a933990a972b32e: exec:
> "auplink": executable file not found in $PATH
> WARN[0021] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> 966252993f7d722a70746d8fa2158debdb822d538eb0d685271adf6fbd95cd3a-init:
> exec: "auplink": executable file not found in $PATH
> WARN[0021] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> 966252993f7d722a70746d8fa2158debdb822d538eb0d685271adf6fbd95cd3a: exec:
> "auplink": executable file not found in $PATH
> INFO[0021] No non-localhost DNS nameservers are left in resolv.conf. Using
> default external servers : [nameserver 8.8.8.8 nameserver 8.8.4.4]
> INFO[0021] IPv6 enabled; Adding default IPv6 external servers :
> [nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844]
> WARN[0102] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/
> 966252993f7d722a70746d8fa2158debdb822d538eb0d685271adf6fbd95cd3a: exec:
> "auplink": executable file not found in $PATH
>
> Regards,
> Dhinakar
>
> On Thu, Mar 2, 2017 at 2:01 PM, Bird, Timothy <Tim.Bird at sony.com> wrote:
>
>> Note: I'm copying this to the fuego list.  We're moving Fuego-specific
>> traffic from the ltsi-dev mailing list to the fuego list, so in the future
>> you should send just to the fuego at lists.linuxfoundation.org list.
>>
>> > -----Original Message-----
>> > From dhinakar k on Wednesday, March 01, 2017 8:03 PM
>> > I am trying to install and evaluate Fuego on my Ubuntu 16.04 LTS
>> (64-bit) PC.
>> >
>> > The PC has git, docker.io <http://docker.io> , openjdk-7 installed in
>> it. Any
>> > other per-requisites needed?
>>
>> Not that I'm aware of.  Actually, the openjdk on your host shouldn't be
>> needed.
>> The fuego install script installs the openjdk used by jenkins into the
>> docker container as part of the Debian jesse installation.
>>
>> See comments below...
>>
>> >
>> >
>> > I followed the steps mentioned in the 'Fuego Quickstart Guide'
>> > http://bird.org/fuego/Fuego_Quickstart_Guide
>> >
>> > $ git clone https://bitbucket.org/tbird20d/fuego.git
>> > $ cd fuego ; ./install.sh
>> >
>> > I got the below errors even after updating the sources.list file with
>> relevant
>> > links.
>> >
>> > ~/fuego$ ./install.sh
>> > Sending build context to Docker daemon 105.1 MB
>> > Step 1 : FROM debian:jessie
>> >  ---> 978d85d02b87
>> > Step 2 : MAINTAINER tim.bird at am.sony.com
>> > <mailto:tim.bird at am.sony.com>
>> >  ---> Using cache
>> >  ---> e1dab8cdbab1
>> > Step 3 : ARG HTTP_PROXY
>> >  ---> Using cache
>> >  ---> 5ef46686acdf
>> > Step 4 : ENV INST_FUEGO_ENGINE_PATH /home/jenkins
>> >  ---> Using cache
>> >  ---> d12194b4c9bd
>> > Step 5 : ENV INST_FUEGO_FRONTEND_PATH /var/lib/jenkins
>> >  ---> Using cache
>> >  ---> c3cff966348a
>> > Step 6 : ENV URL_PREFIX /fuego
>> >  ---> Using cache
>> >  ---> d47cf186937a
>> > Step 7 : WORKDIR /fuego-install
>> >  ---> Using cache
>> >  ---> c2ff647749ac
>> > Step 8 : RUN dpkg --add-architecture i386
>> >  ---> Using cache
>> >  ---> 681941b6cf9d
>> > Step 9 : RUN echo deb http://ftp.us.debian.org/debian jessie main
>> non-free
>> > >> /etc/apt/sources.list
>>
>> I'm not sure if this is the issue, but you might want to try a different
>> debian
>> repository (not the one in the US).  This line in the Dockerfile
>> specifies to
>> use ftp.us.debian.org as the place to download Jessie from, to populate
>> the docker container.  I'm not sure where you are located, but there might
>> be a better (more reliable for your location) repository.
>>
>> The repositories on your host aren't used for this operation, only this
>> one
>> that is put into the container prior to doing the main Jessie package
>> download.
>>
>> >  ---> Using cache
>> >  ---> af015ea7d7a7
>> > Step 10 : RUN if [ -n "$HTTP_PROXY" ]; then echo 'Acquire::http::proxy
>> > "'$HTTP_PROXY'";' > /etc/apt/apt.conf.d/80proxy; fi
>> >  ---> Using cache
>> >  ---> ed37635c1c23
>> > Step 11 : RUN DEBIAN_FRONTEND=noninteractive apt-get update && apt-
>> > get -yV install apt-utils daemon gcc make python-paramiko python-lxml
>> > python-simplejson python-matplotlib libtool xmlstarlet autoconf automake
>> > rsync openjdk-7-jre openjdk-7-jdk iperf netperf netpipe-tcp
>> texlive-latex-
>> > base sshpass wget git diffstat sudo net-tools vim openssh-server curl
>> inotify-
>> > tools
>> >  ---> Running in e672ed2945a2
>> > Err http://ftp.us.debian.org jessie InRelease
>> >
>> > Err http://security.debian.org jessie/updates InRelease
>> >
>> > Err http://ftp.us.debian.org jessie Release.gpg
>> >   Could not resolve 'ftp.us.debian.org <http://ftp.us.debian.org> '
>> > Err http://security.debian.org jessie/updates Release.gpg
>> >   Could not resolve 'security.debian.org <http://security.debian.org> '
>> > Err http://deb.debian.org jessie InRelease
>> >
>> > Err http://deb.debian.org jessie-updates InRelease
>> >
>> > Err http://deb.debian.org jessie Release.gpg
>> >   Could not resolve 'deb.debian.org <http://deb.debian.org> '
>> > Err http://deb.debian.org jessie-updates Release.gpg
>> >   Could not resolve 'deb.debian.org <http://deb.debian.org> '
>> > Reading package lists...
>> > Can you please guide me what is the reason?
>>
>> I haven't seen this message, but it looks a lot like the errors reported
>> in
>> this docker issue: https://github.com/docker/docker/issues/19481
>>
>> That one looks like it has to do with the proxy settings not working for
>> docker
>> for installing Debian in a container.  Are you using a proxy?  If so, can
>> you
>> check to see if the docker build is correctly identifying your proxy?
>>
>> There is code in the Dockerfile to set up the proxy for apt, but maybe
>> there's
>> an issue with this.
>>
>> > Infact there is no 'InRelease' in the below link, Iam not sure from
>> where it is
>> > picking it.
>> > http://ftp.us.debian.org jessie InRelease
>> >
>> >
>> > Here is the snapshot of my sources.list file.
>>
>> The docker container creation should not be using your sources.list file,
>> but the one it installed in the container image in step 9.
>>
>> > Thanks a lot, in advance.
>> > Regards,
>> > Dhinakar
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20170302/b76abe50/attachment-0001.html>


More information about the Fuego mailing list