[Fuego] Regarding changing jenkins service port change (from 8080 -> 8082)

Tim.Bird at sony.com Tim.Bird at sony.com
Wed Feb 27 02:47:40 UTC 2019



> -----Original Message-----
> From: daniel.sangorrin at toshiba.co.jp
> Hi Dhinakar,
> 
> > [FAIL] Starting network benchmark server failed!
> 
> This failure is normal, because you are trying to start a netperf server on two
> containers at the same time and only one can serve that port. Given that the
> netperf tests do not specify the port I think that you can safely ignore the fail
> message because the target will connect to whatever netperf server is
> available.
The usual reason for the failure is that the netperf server is already running
on the host.  This is actually a bit strange, IMHO, as most hosts will not be running
netperf tests on other machines against themselves.  So this seems rather
strange to default this service to 'on' on most desktop distributions of Linux.

However, the upshot of all this is that the most common scenario is that there
is a netperf server available, and the tests will run OK.  I usually ignore this.
(However, in my own scripts that start containers I usually check if the netperf
server is running on the host and stop it, to avoid this error.)

> 
> Actually, the idea of running netperf on the docker container is quite hacky
> itself.

The mechanism here for managing the netperf server is indeed a bit hacky.

The philosophy is as follows:  The Fuego docker container is intended to have
all required elements (outside the DUT) for performing tests.  netperf is usually configured
with a single server, and it's appropriate for the docker container to have a netperf
server already configured for use by tests.  However, there really should be a mechanism
for managing access to that server, and we're creeping up on it with the 'ftc reserve-resource'
and 'ftc release-resource' functionality.  The reason it's not finished yet is that you need to
couple this with job scheduling, and that hasn't been added to ftc (or Fuego in general).  We use
Jenkins to schedule the boards (or maybe LAVA), but when dealing with off-board services,
those should be scheduled along with the board.

In any event, hopefully generic resource scheduling will get added to Fuego soon.
Then the netperf server could reside anywhere in the lab (in the container, on the host,
or on another LAB machine or DUT), and it could get scheduled and utilized by Fuego during
testing.

 -- Tim


> > -----Original Message-----
> > From: sangorrin daniel(サンゴリン ダニエル ○SWC□OST)
> > Sent: Friday, February 22, 2019 2:52 PM
> > To: dhinakar.k at samsung.com
> > Cc: fuego at lists.linuxfoundation.org
> > Subject: RE: RE: RE: RE: [Fuego] Regarding changing jenkins service port
> change (from 8080 -> 8082)
> >
> > Hi Dhinakar,
> >
> > > -----Original Message-----
> > > From: Dhinakar Kalyanasundaram <dhinakar.k at samsung.com>
> > > Sent: Friday, February 22, 2019 2:40 PM
> > > To: sangorrin daniel(サンゴリン ダニエル ○SWC□OST)
> <daniel.sangorrin at toshiba.co.jp>
> > > Cc: Dhinakar Kalyanasundaram <dhinakar.k at samsung.com>;
> fuego at lists.linuxfoundation.org
> > > Subject: RE: RE: RE: RE: [Fuego] Regarding changing jenkins service port
> change (from 8080 -> 8082)
> > >
> > > Hi Daniel,
> > >
> > >
> > >
> > > It works perfectly fine (working on port 8090) after disabling the Cache.
> >
> > Sorry, I am confused. What is working fine?. The next branch, or the
> manual changes that you did?
> >
> > > But as mentioned before if one more instance is started say listening on
> 8080, network benchmark server fails
> > > to start (as shown below).
> > > So this port change should also be applied for 'network benchmark
> server'.
> >
> > OK, thanks. Let me investigate and I will answer you.
> >
> > Thanks,
> > Daniel
> >
> >
> > >
> > > Thanks.
> > >
> > >
> > >
> > >
> > dhinakar at userl2:~/fuego$ <mailto:dhinakar at userl2:~/fuego$>  ./fuego-
> host-scripts/docker-start-containe
> > > r.sh docker-container-7thDec2018
> > > Starting Fuego container (docker-container-7thDec2018)
> > > [sudo] password for dhinakar:
> > > [ ok ] Starting Jenkins Continuous Integration Server: jenkins.
> > > [FAIL] Starting network benchmark server failed!
> > >
> > >
> > > Regards,
> > >
> > > Dhinakar
> > >
> > >
> > >
> > >
> > >
> > > --------- Original Message ---------
> > >
> > > Sender : Dhinakar Kalyanasundaram <dhinakar.k at samsung.com> Staff
> Engineer/FDS SW /SSIR/Samsung
> > > Electronics
> > >
> > > Date : 2019-02-22 10:32 (GMT+5:30)
> > >
> > > Title : RE: RE: RE: [Fuego] Regarding changing jenkins service port change
> (from 8080 -> 8082)
> > >
> > >
> > >
> > > Yeah sorry, I also just noticed it after sending the email and rerunning the
> install now with 'Cache' disabled.
> > >
> > > Thanks for the prompt response.
> > >
> > >
> > >
> > > Regards,
> > >
> > > Dhinakar
> > >
> > >
> > >
> > >
> > >
> > > --------- Original Message ---------
> > >
> > > Sender : daniel.sangorrin at toshiba.co.jp
> <daniel.sangorrin at toshiba.co.jp>
> > >
> > > Date : 2019-02-22 09:59 (GMT+5:30)
> > >
> > > Title : RE: RE: [Fuego] Regarding changing jenkins service port change
> (from 8080 -> 8082)
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Dhinakar Kalyanasundaram <dhinakar.k at samsung.com>
> > > > Sent: Friday, February 22, 2019 1:24 PM
> > > > To: sangorrin daniel(サンゴリン ダニエル ○SWC□OST)
> <daniel.sangorrin at toshiba.co.jp>
> > > > Cc: Dhinakar Kalyanasundaram <dhinakar.k at samsung.com>;
> fuego at lists.linuxfoundation.org
> > > > Subject: RE: RE: [Fuego] Regarding changing jenkins service port change
> (from 8080 -> 8082)
> > > >
> > > > Hi Daniel,
> > > >
> > > >
> > > >
> > > > I tried the your patch on the 'next' branch but it seems Jenkins is still
> running on 8080 port.
> > > >
> > > > Please check the log of 'install.sh'
> > > >
> > > > I want to run Jenkins on port 8090 and if I create and start the container
> after installing the image, it seems
> > > to
> > > > be listening on 8080 port.
> > > >
> > > > In the log also I see that 'Step 24/62 : ARG JENKINS_PORT=8080' even
> though it says 'Using Port 8090'
> > in
> > > the
> > > > beginning.
> > > >
> > > > Probably 'ENV JENKINS_PORT=$JENKINS_PORT' is not getting assigned
> properly.
> > > >
> > > >
> > > >
> > > > FYI, cache is already commented in docker-build-image.sh (as shown
> below),
> > > >
> > > > #NO_CACHE=--no-cache
> > >
> > > Sorry, not comment out. Uncomment it.
> > >
> > > Regards,
> > > Daniel
> > >
> > >
> > >
> > >
> > >
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Dhinakar
> > > >
> > > >
> > > >
> > > > dhinakar at userl2:~/daniel-fuego/fuego$
> <mailto:dhinakar at userl2:~/daniel-fuego/fuego$>  ./install.sh
> > > > daniel-fuego-image-20thfeb2019 8090
> > > > Using Port 8090
> > > > [sudo] password for dhinakar:
> > > > Sorry, try again.
> > > > [sudo] password for dhinakar:
> > > > Sending build context to Docker daemon  557.5MB
> > > > Step 1/62 : FROM debian:jessie
> > > >  ---> 39db55273026
> > > > Step 2/62 : MAINTAINER tim.bird at sony.com
> <mailto:tim.bird at sony.com>
> > > >  ---> Using cache
> > > >  ---> 2178f591a2ab
> > > > Step 3/62 : ARG HTTP_PROXY
> > > >  ---> Using cache
> > > >  ---> 1e9470e7996b
> > > > Step 4/62 : ENV http_proxy ${HTTP_PROXY}
> > > >  ---> Using cache
> > > >  ---> 0513bcdd950f
> > > > Step 5/62 : ENV https_proxy ${HTTP_PROXY}
> > > >  ---> Using cache
> > > >  ---> e5f4eaf2230d
> > > > Step 6/62 : ARG DEBIAN_FRONTEND=noninteractive
> > > >  ---> Using cache
> > > >  ---> 07de86ab3f2d
> > > > Step 7/62 : WORKDIR /
> > > >  ---> Using cache
> > > >  ---> 904d9c4a8c26
> > > > Step 8/62 : RUN echo deb http://httpredir.debian.org/debian jessie
> main non-free > /etc/apt/sources.list
> > > >  ---> Using cache
> > > >  ---> e0b40e49b817
> > > > Step 9/62 : RUN echo deb http://httpredir.debian.org/debian jessie-
> updates main non-free >>
> > > > /etc/apt/sources.list
> > > >  ---> Using cache
> > > >  ---> d03e90662475
> > > > Step 10/62 : RUN echo deb http://security.debian.org/ jessie/updates
> main >> /etc/apt/sources.list
> > > >  ---> Using cache
> > > >  ---> 6f080c2040a6
> > > > Step 11/62 : RUN if [ -n "$HTTP_PROXY" ]; then echo
> 'Acquire::http::proxy "'$HTTP_PROXY'";' >
> > > > /etc/apt/apt.conf.d/80proxy; fi
> > > >  ---> Using cache
> > > >  ---> 39848694a182
> > > > Step 12/62 : RUN apt-get update && apt-get -yV install  apt-utils
> daemon gcc make cmake
> > python-paramiko
> > > > python-lxml python-simplejson   python-matplotlib python-serial
> python-yaml python-openpyxl
> > > > python-requests python-reportlab libtool xmlstarlet autoconf
> automake rsync openjdk-7-jre openjdk-7-jdk
> > > > iperf netperf netpipe-tcp sshpass wget git diffstat sudo net-tools vim
> curl     inotify-tools g++ bzip2 bc
> > > libaio-dev
> > > > gettext pkg-config libglib2.0-dev     time python-pip python-xmltodict at
> minicom lzop bsdmainutils
> > > > u-boot-tools      mc netcat lava-tool openssh-server python-
> parsedatetime         libsdl1.2-dev
> > > libcairo2-dev
> > > > libxmu-dev libxmuu-dev iperf3   bison flex libelf-dev libssl-dev
> > > >  ---> Using cache
> > > >  ---> 90b01f4de038
> > > > Step 13/62 : RUN pip install python-jenkins==0.4.14
> > > >  ---> Using cache
> > > >  ---> 911629d1ea69
> > > > Step 14/62 : RUN pip install filelock
> > > >  ---> Using cache
> > > >  ---> d11bead1ba4c
> > > > Step 15/62 : RUN pip install flake8
> > > >  ---> Using cache
> > > >  ---> b5082750430c
> > > > Step 16/62 : RUN /bin/bash -c 'echo "dash dash/sh boolean false" |
> debconf-set-selections ;
> > dpkg-reconfigure
> > > > dash'
> > > >  ---> Using cache
> > > >  ---> 80f57db54ab4
> > > > Step 17/62 : RUN if [ -n "$HTTP_PROXY" ]; then echo "use_proxy = on"
> >> /etc/wgetrc; fi
> > > >  ---> Using cache
> > > >  ---> 5ea03342dd30
> > > > Step 18/62 : RUN if [ -n "$HTTP_PROXY" ]; then echo -e
> > > > "http_proxy=$HTTP_PROXY\nhttps_proxy=$HTTP_PROXY" >>
> /etc/environment; fi
> > > >  ---> Using cache
> > > >  ---> 47ff3af11381
> > > > Step 19/62 : RUN echo -e "JENKINS_PORT=$JENKINS_PORT" >>
> /etc/environment
> > > >  ---> Using cache
> > > >  ---> afd0442a477b
> > > > Step 20/62 : ARG user=jenkins
> > > >  ---> Using cache
> > > >  ---> 9df1b6250a42
> > > > Step 21/62 : ARG group=jenkins
> > > >  ---> Using cache
> > > >  ---> 3f23dd4f668c
> > > > Step 22/62 : ARG uid=1000
> > > >  ---> Using cache
> > > >  ---> e2b2d5de8863
> > > > Step 23/62 : ARG gid=${uid}
> > > >  ---> Using cache
> > > >  ---> ad63a38b1e16
> > > > Step 24/62 : ARG JENKINS_PORT=8080
> > > >  ---> Using cache
> > > >  ---> da215d42e0cb
> > > > Step 25/62 : ARG JENKINS_VERSION=2.32.1
> > > >  ---> Using cache
> > > >  ---> 226358157dd3
> > > > Step 26/62 : ARG
> JENKINS_SHA=bfc226aabe2bb089623772950c4cc13aee613af1
> > > >  ---> Using cache
> > > >  ---> afa0745e96fb
> > > > Step 27/62 : ARG
> > > > JENKINS_URL=https://pkg.jenkins.io/debian-
> stable/binary/jenkins_${JENKINS_VERSION}_all.deb
> > > >  ---> Using cache
> > > >  ---> 37a1b1882ce6
> > > > Step 28/62 : ENV JENKINS_HOME=/var/lib/jenkins
> > > >  ---> Using cache
> > > >  ---> eab82e41f151
> > > > Step 29/62 : ENV JENKINS_PORT=$JENKINS_PORT
> > > >  ---> Using cache
> > > >  ---> 5073105b96d5
> > > > Step 30/62 : RUN getent group ${gid} >/dev/null || groupadd -g ${gid}
> ${group}
> > > >  ---> Using cache
> > > >  ---> 6635388e0706
> > > > Step 31/62 : RUN useradd -l -m -d "${JENKINS_HOME}" -u ${uid} -g
> ${gid} -G sudo -s /bin/bash ${user}
> > > >  ---> Using cache
> > > >  ---> 79480c502ab1
> > > > Step 32/62 : RUN wget -nv ${JENKINS_URL}
> > > >  ---> Using cache
> > > >  ---> d8e49cc590ff
> > > > Step 33/62 : RUN echo "${JENKINS_SHA}
> jenkins_${JENKINS_VERSION}_all.deb" | sha1sum -c -
> > > >  ---> Using cache
> > > >  ---> c70ff0422e30
> > > > Step 34/62 : RUN printf "#!/bin/sh\nexit 0" > /usr/sbin/policy-rc.d
> > > >  ---> Using cache
> > > >  ---> c0f2f311661f
> > > > Step 35/62 : RUN ls /var/lib/jenkins/plugins || true
> > > >  ---> Using cache
> > > >  ---> f26ef6ad6135
> > > > Step 36/62 : RUN dpkg -i jenkins_${JENKINS_VERSION}_all.deb
> > > >  ---> Using cache
> > > >  ---> 9721f842955c
> > > > Step 37/62 : RUN rm jenkins_${JENKINS_VERSION}_all.deb
> > > >  ---> Using cache
> > > >  ---> fa0645994a3f
> > > > Step 38/62 : RUN ls /var/lib/jenkins/plugins || true
> > > >  ---> Using cache
> > > >  ---> 8949d2cb1c3b
> > > > Step 39/62 : RUN git clone https://github.com/tbird20d/ttc.git
> /usr/local/src/ttc
> > > >  ---> Using cache
> > > >  ---> 46752d50d34e
> > > > Step 40/62 : RUN /usr/local/src/ttc/install.sh /usr/local/bin
> > > >  ---> Using cache
> > > >  ---> 08d623801cc9
> > > > Step 41/62 : RUN perl -p -i -e "s#config_dir = \"/etc\"#config_dir =
> \"/fuego-ro/conf\"#"
> > /usr/local/bin/ttc
> > > >  ---> Using cache
> > > >  ---> 4834ec713157
> > > > Step 42/62 : RUN /bin/bash -c 'git clone
> https://github.com/frowand/serio.git /usr/local/src/serio ;
> > chown
> > > -R
> > > > jenkins /usr/local/src/serio ; cp /usr/local/src/serio/serio /usr/local/bin/
> ; ln -s /usr/local/bin/serio
> > > > /usr/local/bin/sercp ; ln -s /usr/local/bin/serio /usr/local/bin/sersh'
> > > >  ---> Using cache
> > > >  ---> 1e4f99bee0ae
> > > > Step 43/62 : RUN /bin/bash -c 'git clone
> https://github.com/tbird20d/serlogin.git /usr/local/src/serlogin ;
> > > > chown -R jenkins /usr/local/src/serlogin ; cp
> /usr/local/src/serlogin/serlogin /usr/local/bin'
> > > >  ---> Using cache
> > > >  ---> 56f84e84f3b8
> > > > Step 44/62 : RUN /bin/bash -c 'git clone
> https://github.com/tbird20d/fserver.git /usr/local/lib/fserver ; ln
> > -s
> > > > /usr/local/lib/fserver/start_local_bg_server
> /usr/local/bin/start_local_bg_server'
> > > >  ---> Using cache
> > > >  ---> 371ed875a557
> > > > Step 45/62 : RUN source /etc/default/jenkins &&
> JENKINS_ARGS="$JENKINS_ARGS
> > > --prefix=/fuego"
> > > > &&         sed -i -e
> "s#JENKINS_ARGS.*#JENKINS_ARGS\=\"${JENKINS_ARGS}\"#g"
> > > > /etc/default/jenkins
> > > >  ---> Using cache
> > > >  ---> 8335752d8102
> > > > Step 46/62 : RUN source /etc/default/jenkins &&
> JAVA_ARGS="$JAVA_ARGS
> > > > -Djenkins.install.runSetupWizard=false" &&        if [ -n "$HTTP_PROXY" ];
> then
> > > > PROXYSERVER=$(echo $http_proxy | sed -E 's/^http://' | sed -E
> 's/\///g' | sed -E 's/(.*):(.*)/\1/') &&
> > > > PROXYPORT=$(echo $http_proxy | sed -E 's/^http://' | sed -E 's/\///g' |
> sed -E 's/(.*):(.*)/\2/') &&
> > > > JAVA_ARGS="$JAVA_ARGS -Dhttp.proxyHost="${PROXYSERVER}" -
> Dhttp.proxyPort="${PROXYPORT}"
> > > > -Dhttps.proxyHost="${PROXYSERVER}" -
> Dhttps.proxyPort="${PROXYPORT};         fi &&   sed -i -e
> > > > "s#^JAVA_ARGS.*#JAVA_ARGS\=\"${JAVA_ARGS}\"#g"
> /etc/default/jenkins;
> > > >  ---> Using cache
> > > >  ---> 537422269297
> > > > Step 47/62 : RUN sed -i -e "s#8080#$JENKINS_PORT#g"
> /etc/default/jenkins
> > > >  ---> Using cache
> > > >  ---> 7a4ab3d2bf82
> > > > Step 48/62 : COPY frontend-install/plugins/flot-plotter-plugin/flot.hpi
> /tmp
> > > >  ---> Using cache
> > > >  ---> c713ddd52f86
> > > > Step 49/62 : COPY frontend-install/install-plugins.sh     frontend-
> install/jenkins-support
> > > > frontend-install/clitest     /usr/local/bin/
> > > >  ---> Using cache
> > > >  ---> f220a8cbe4c9
> > > > Step 50/62 : RUN service jenkins start &&       sleep 30 &&     sudo -u
> jenkins java -jar
> > > > /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s
> http://localhost:$JENKINS_PORT/fuego install-plugin
> > > > /tmp/flot.hpi &&     sleep 10 &&     service jenkins stop
> > > >  ---> Using cache
> > > >  ---> 0d9ec9a1db38
> > > > Step 51/62 : RUN /usr/local/bin/install-plugins.sh ant:1.7
> bouncycastle-api:2.16.2
> > > > description-setter:1.10     display-url-api:2.1.0     external-monitor-
> job:1.7     greenballs:1.15
> > > > icon-shim:2.0.3     javadoc:1.4     junit:1.21     ldap:1.17     mailer:1.20
> matrix-auth:1.7
> > > > matrix-project:1.12     antisamy-markup-formatter:1.5     pam-auth:1.3
> pegdown-formatter:1.3
> > > > script-security:1.35     structs:1.10     windows-slaves:1.3.1
> > > >  ---> Using cache
> > > >  ---> 256294d5b07b
> > > > Step 52/62 : RUN service jenkins start && sleep 30 &&     rm
> $JENKINS_HOME/plugins/flot/flot/mod.js
> > &&
> > > > ln -s /fuego-core/scripts/mod.js
> $JENKINS_HOME/plugins/flot/flot/mod.js
> > > >  ---> Using cache
> > > >  ---> af027ed0f4df
> > > > Step 53/62 : RUN ln -s /fuego-rw/logs
> $JENKINS_HOME/userContent/fuego.logs
> > > >  ---> Using cache
> > > >  ---> bbfe85893379
> > > > Step 54/62 : COPY docs/fuego-docs.pdf
> $JENKINS_HOME/userContent/docs/fuego-docs.pdf
> > > >  ---> Using cache
> > > >  ---> d5958a27fc41
> > > > Step 55/62 : RUN ln -s /fuego-core/scripts/ftc /usr/local/bin/
> > > >  ---> Using cache
> > > >  ---> 461f56c640b3
> > > > Step 56/62 : COPY frontend-install/config.xml
> $JENKINS_HOME/config.xml
> > > >  ---> Using cache
> > > >  ---> 499ebdd37e05
> > > > Step 57/62 : COPY frontend-
> install/jenkins.model.JenkinsLocationConfiguration.xml
> > > > $JENKINS_HOME/jenkins.model.JenkinsLocationConfiguration.xml
> > > >  ---> Using cache
> > > >  ---> b12062a58596
> > > > Step 58/62 : RUN sed -i -e "s#8080#$JENKINS_PORT#g"
> > > > $JENKINS_HOME/jenkins.model.JenkinsLocationConfiguration.xml
> > > >  ---> Using cache
> > > >  ---> 73430b1dc0dd
> > > > Step 59/62 : RUN chown -R jenkins:jenkins $JENKINS_HOME/
> > > >  ---> Using cache
> > > >  ---> b15723367b05
> > > > Step 60/62 : RUN ln -s /fuego-ro/scripts/fuego-lava-target-setup
> /usr/local/bin
> > > >  ---> Using cache
> > > >  ---> 92e39aa956d2
> > > > Step 61/62 : RUN ln -s /fuego-ro/scripts/fuego-lava-target-teardown
> /usr/local/bin
> > > >  ---> Using cache
> > > >  ---> bbadc989e914
> > > > Step 62/62 : ENTRYPOINT service jenkins start && service netperf start
> && iperf3 -V -s -D -f M && /bin/bash
> > > >  ---> Using cache
> > > >  ---> 574ebf64383a
> > > > Successfully built 574ebf64383a
> > > > Successfully tagged daniel-fuego-image-20thfeb2019:latest
> > > > Error response from daemon: Conflict. The container name "/daniel-
> fuego-image-20thfeb2019-container"
> > is
> > > > already in use by container
> > >
> "a3645ed463ebd70fe1fa0bed88c873c98d1aa863a4dc4773c87296b0a13011e3".
> > > > You have to remove (or rename) that container to be able to reuse that
> name.
> > > > Could not create fuego-container. See error messages.
> > > > Docker container 'daniel-fuego-image-20thfeb2019-container' is ready
> with Fuego installation.
> > > > To start, run: ./start.sh daniel-fuego-image-20thfeb2019-container
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Dhinakar
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --------- Original Message ---------
> > > >
> > > > Sender : daniel.sangorrin at toshiba.co.jp
> <daniel.sangorrin at toshiba.co.jp>
> > > >
> > > > Date : 2019-02-20 12:33 (GMT+5:30)
> > > >
> > > > Title : RE: [Fuego] Regarding changing jenkins service port change (from
> 8080 -> 8082)
> > > >
> > > >
> > > >
> > > > Hello Dhinakar,
> > > >
> > > > > From: fuego-bounces at lists.linuxfoundation.org <fuego-
> bounces at lists.linuxfoundation.org> On Behalf
> > Of
> > > > > Dhinakar Kalyanasundaram
> > > > > Sent: Tuesday, February 19, 2019 10:59 PM
> > > >  > Dear Fuego Users,
> > > > >
> > > > >
> > > > >
> > > > > I want to run multiple instances of fuego (in one powerful server) to
> cater to different projects (which need
> > > to
> > > > be kept
> > > > > separate for security).
> > > > >
> > > > > In this regard I thought I can assign a unique port for each instance,
> for e.g. 8080 -> Project1, 8081 ->
> > > > Project2 etc.
> > > > >
> > > > > If there is any other better way to achieve the objective please let me
> know.
> > > > >
> > > > > I modified all occurrences of port 8080 to 8082 under fuego
> (Dockerfile, ftc, common.sh etc.) &
> > fuego-core
> > > > > directories in my existing installation.
> > > > >
> > > > > Recreated the container -> ./fuego-host-scripts/docker-create-usb-
> privileged-container.sh
> > > > > containerbackup-15thfeb2019 container-19thfeb2019
> > > > >
> > > > > And Started it -> ./fuego-host-scripts/docker-start-container.sh
> container-19thfeb2019
> > > > >
> > > > > But it is still running on port 8080 only.
> > > > >
> > > > > The 'containerbackup-15thfeb2019' image that I used to create the
> new container was running on port
> > > 8080,
> > > > could
> > > > > it be because of it?
> > > > >
> > > > > I thought if I make changes in 'fuego', 'fuego-core' directories and
> recreate the container & start, it should
> > > > listen on
> > > > > port 8082.
> > > > >
> > > > > Should I create a new image after the modification and then create a
> container and start?
> > > > >
> > > > > Can someone help in this regard?
> > > >
> > > > I just sent a few patches to support the creation of Fuego images using
> separate TCP ports.
> > > > They are on the "next" branch of my repository
> (https://bitbucket.org/nirrognas/) for now.
> > > > Could you give them a try?
> > > >
> > > > Thanks,
> > > > Daniel
> > > >
> > > >
> > > > >
> > > > > Thanks.
> > > > >
> > > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Dhinakar
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> kar.k&do=bWFpbElEPTIwMTkwMj
> > > > E5
> > > > >
> > > >
> > >
> >
> MTM1OTE1ZXBjbXM1cDg4N2Y5ZDQxNjA5N2U2NzIxODNkYWYwN2E5OGU3
> MzQ4NyZyZWNpcGllbnRBZGRyZ
> > > > XNzP
> > > > > WZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_>
> > > >
> > > >
> > > >
> > > >
> > >
> >
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> kar.k&do=bWFpbElEPTIwMTkwMj
> > > I
> > > >
> > >
> >
> yMDQyNDE3ZXBjbXM1cDVmMzYwMDMwOGIwNWQ0YTRmM2NmMWY4Mj
> QyNTMzM2NlOCZyZWNpcGllbnRBZ
> > > > GRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS5jby5qcA__>
> > >
> > >
> > >
> > >
> >
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> kar.k&do=bWFpbElEPTIwMTkwMj
> > I
> > >
> >
> yMDU0MDE1ZXBjbXM1cDM1NTNkMWI3MTY1N2IwYzYxMmVmZjU0MTEzY2
> Q1YTRiOCZyZWNpcGllbnRBZGRyZ
> > > XNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS5jby5qcA__>
> _______________________________________________
> Fuego mailing list
> Fuego at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego


More information about the Fuego mailing list