<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">​Hello, Tim, hope everything is going well.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Can you please give it a couple more tries by checking out the two</div><div class="gmail_default" style="font-family:monospace,monospace">new branches that I&#39;ve just pushed to our fuego repo?</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">You can just fetch them, checkout and run, because</div><div class="gmail_default" style="font-family:monospace,monospace">we haven&#39;t force pushed anything since yesterday.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">They have one commit each (above fuego-test branch),</div><div class="gmail_default" style="font-family:monospace,monospace">with a potential fix to the problem.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">The repo/branches are these ones:</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default"><font face="monospace, monospace">* <a href="https://bitbucket.org/profusionmobi/fuego/branch/chown-all?dest=fuego-test">https://bitbucket.org/profusionmobi/fuego/branch/chown-all?dest=fuego-test</a></font><br></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">  git fetch &amp;&amp; git checkout chown-all</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">  On this patch we&#39;re just using `chown -R --from` to chown all jenkins</font></div><div class="gmail_default"><font face="monospace, monospace">  files that </font><span style="font-family:monospace,monospace">may still exist outside of the directories that we were chowning</span></div><div class="gmail_default"><span style="font-family:monospace,monospace">  so far.</span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">  Please Try This One First. And if it works, great. If not, please</span></div><div class="gmail_default"><span style="font-family:monospace,monospace">  try the next branch (below).</span></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">* <a href="https://bitbucket.org/profusionmobi/fuego/branch/jenkins-user-on-build?dest=fuego-test">https://bitbucket.org/profusionmobi/fuego/branch/jenkins-user-on-build?dest=fuego-test</a></font></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">  git fetch &amp;&amp; git checkout jenkins-user-on-build</span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><div class="gmail_default" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><font face="monospace, monospace">  This patch is almost a &#39;clean revert&#39; of the patch that moved the jenkins uid</font></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><font face="monospace, monospace">  mapping to the entrypoint. We&#39;re just setting the correct jenkins id during</font></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><font face="monospace, monospace">  docker build, by passing uid/gid through the docker-build-image.sh script and</font></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><font face="monospace, monospace">  reading them through the Dockerfile.</font></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><font face="monospace, monospace"><br></font></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><font face="monospace, monospace">  This one should probably solve the issue, given that no ownership will need to</font></div><div class="gmail_default" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><font face="monospace, monospace">  be changed, since Jenkins starts for the first time with the correct user already.</font></div></span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">Please just make sure to run a `git clean -dxf` in the repo before running,</span></div><div class="gmail_default"><span style="font-family:monospace,monospace">to remove anything that jenkins might have written to fuego-rw.</span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">I&#39;m also attaching the patches, for you to apply them directly if you prefer.</span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace"><br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">Thank you very much</span></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 8, 2018 at 9:51 PM,  <span dir="ltr">&lt;<a href="mailto:Tim.Bird@sony.com" target="_blank">Tim.Bird@sony.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I just tried to everything on Ubuntu 16.04, using docker version 1.13.1,<br>
and I get the same problem.<br>
<br>
When I exit the container, and try to restart it, Jenkins fails to start, and the<br>
log says:<br>
java.io.FileNotFoundException: /var/cache/jenkins/war/META-<wbr>INF/MANIFEST.MF<br>
<br>
The file is there, owned by jenkins.jenkins.<br>
<br>
Here is more information:<br>
jenkins@timdesk:/var/cache/<wbr>jenkins$ ls -la<br>
ls: cannot access war: Permission denied<br>
total 8<br>
drwxr-x---  4 jenkins jenkins 4096 Mar  9 00:37 .<br>
drwxr-xr-x 20 root   root    4096 Mar  9 00:37 ..<br>
d?????????  ? ?        ?           ?                ? war<br>
jenkins@timdesk:/var/cache/<wbr>jenkins$l id<br>
uid=1000(jenkins) gid=1000(jenkins) groups=1000(jenkins)<br>
------<br>
<br>
So, we&#39;ve still got a permission problem in here somewhere.<br>
 -- Tim<br>
<div><div class="h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href="mailto:Tim.Bird@sony.com">Tim.Bird@sony.com</a><br>
&gt;<br>
&gt; Same behavior.<br>
&gt;  -- Tim<br>
&gt;<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href="mailto:fuego-bounces@lists.linuxfoundation.org">fuego-bounces@lists.<wbr>linuxfoundation.org</a> [mailto:<a href="mailto:fuego-">fuego-</a><br>
&gt; &gt; <a href="mailto:bounces@lists.linuxfoundation.org">bounces@lists.linuxfoundation.<wbr>org</a>] On Behalf Of Guilherme Camargo<br>
&gt; &gt; Sent: Thursday, March 08, 2018 2:20 PM<br>
&gt; &gt; To: Bird, Timothy &lt;<a href="mailto:Tim.Bird@sony.com">Tim.Bird@sony.com</a>&gt;<br>
&gt; &gt; Cc: <a href="mailto:fuego@lists.linuxfoundation.org">fuego@lists.linuxfoundation.<wbr>org</a><br>
&gt; &gt; Subject: Re: [Fuego] [PATCH 00/11] Add Fuego Functional.fuegotest<br>
&gt; &gt;<br>
&gt; &gt; ​Tim, can you please try to add `--privileged` to the `docker create`​ call on<br>
&gt; &gt; fuego-host-scripts/docker-<wbr>create-container.sh ? This should not be the<br>
&gt; final<br>
&gt; &gt; fix, it&#39;s just for testing.<br>
&gt; &gt;<br>
&gt; &gt; ```<br>
&gt; &gt;<br>
&gt; &gt; sudo docker create -it --name ${DOCKERCONTAINER} \<br>
&gt; &gt;     --privileged \<br>
&gt; &gt;     -v /var/run/docker.sock:/var/run/<wbr>docker.sock \<br>
&gt; &gt;     -v /boot:/boot:ro \<br>
&gt; &gt;     -v $DIR/../fuego-rw:/fuego-rw \<br>
&gt; &gt;     -v $DIR/../fuego-ro:/fuego-ro:ro \<br>
&gt; &gt;     -v $DIR/../../fuego-core:/fuego-<wbr>core:ro \<br>
&gt; &gt;     -e http_proxy=${http_proxy} \<br>
&gt; &gt;     -e https_proxy=${https_proxy:-$<wbr>http_proxy} \<br>
&gt; &gt;     --net=&quot;host&quot; ${DOCKERIMAGE} || \<br>
&gt; &gt;     echo &quot;Could not create fuego-container. See error messages.&quot;<br>
&gt; &gt;<br>
&gt; &gt; ```<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Thanks<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Thu, Mar 8, 2018 at 6:32 PM, &lt;<a href="mailto:Tim.Bird@sony.com">Tim.Bird@sony.com</a><br>
&gt; &gt; &lt;mailto:<a href="mailto:Tim.Bird@sony.com">Tim.Bird@sony.com</a>&gt; &gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;     &gt; -----Original Message-----<br>
&gt; &gt;     &gt; From: <a href="mailto:fuego-bounces@lists.linuxfoundation.org">fuego-bounces@lists.<wbr>linuxfoundation.org</a> &lt;mailto:<a href="mailto:fuego-">fuego-</a><br>
&gt; &gt; <a href="mailto:bounces@lists.linuxfoundation.org">bounces@lists.linuxfoundation.<wbr>org</a>&gt;  [mailto:<a href="mailto:fuego-">fuego-</a> &lt;mailto:<a href="mailto:fuego-">fuego-</a>&gt;<br>
&gt; &gt;     &gt; <a href="mailto:bounces@lists.linuxfoundation.org">bounces@lists.linuxfoundation.<wbr>org</a><br>
&gt; &gt; &lt;mailto:<a href="mailto:bounces@lists.linuxfoundation.org">bounces@lists.<wbr>linuxfoundation.org</a>&gt; ] On Behalf Of Guilherme<br>
&gt; &gt; Campos<br>
&gt; &gt;     &gt; Camargo<br>
&gt; &gt;     &gt; Sent: Wednesday, March 07, 2018 11:55 AM<br>
&gt; &gt;     &gt; To: <a href="mailto:fuego@lists.linuxfoundation.org">fuego@lists.linuxfoundation.<wbr>org</a><br>
&gt; &gt; &lt;mailto:<a href="mailto:fuego@lists.linuxfoundation.org">fuego@lists.<wbr>linuxfoundation.org</a>&gt;<br>
&gt; &gt;     &gt; Subject: [Fuego] [PATCH 00/11] Add Fuego Functional.fuegotest<br>
&gt; &gt;     &gt;<br>
&gt; &gt;     &gt; Hello, Tim<br>
&gt; &gt;     &gt;<br>
&gt; &gt;     &gt; Please see a few more commits that have been added to<br>
&gt; &gt;     &gt; Functional.fuegotest.<br>
&gt; &gt;     &gt; They include bug-fixes and some new tests (Shell and Selenium).<br>
&gt; &gt;     &gt;<br>
&gt; &gt;     &gt; Not sure if you had the chance to take a look at my previous<br>
&gt; &gt; patches yet, but<br>
&gt; &gt;     &gt; if not, please consider using these one instead.<br>
&gt; &gt;     &gt;<br>
&gt; &gt;     &gt; There are many commits, but most of them are pretty small. Please<br>
&gt; &gt; feel<br>
&gt; &gt;     &gt; free to ask me to squash some of them if you prefer.<br>
&gt; &gt;     &gt;<br>
&gt; &gt;     &gt; To run these, you will need to checkout the `fuego-test` branch<br>
&gt; &gt; from<br>
&gt; &gt;     &gt; Profusion&#39;s fuego and fuego-core forks and then simply use fuego<br>
&gt; &gt; as usual to<br>
&gt; &gt;     &gt; add the fuego-test board and the Functional.fuegotest test.<br>
&gt; &gt;     &gt;<br>
&gt; &gt;     &gt; In summary:<br>
&gt; &gt;     &gt;<br>
&gt; &gt;     &gt; On host:<br>
&gt; &gt;     &gt; git clone --branch fuego-test<br>
&gt; &gt; <a href="https://bitbucket.org/profusionmobi/fuego-" rel="noreferrer" target="_blank">https://bitbucket.org/<wbr>profusionmobi/fuego-</a><br>
&gt; &gt; &lt;<a href="https://bitbucket.org/profusionmobi/fuego-" rel="noreferrer" target="_blank">https://bitbucket.org/<wbr>profusionmobi/fuego-</a>&gt;<br>
&gt; &gt;     &gt; core.git<br>
&gt; &gt;     &gt; git clone --branch fuego-test<br>
&gt; &gt; <a href="https://bitbucket.org/profusionmobi/fuego.git" rel="noreferrer" target="_blank">https://bitbucket.org/<wbr>profusionmobi/fuego.git</a><br>
&gt; &gt; &lt;<a href="https://bitbucket.org/profusionmobi/fuego.git" rel="noreferrer" target="_blank">https://bitbucket.org/<wbr>profusionmobi/fuego.git</a>&gt;<br>
&gt; &gt;     &gt; cd fuego<br>
&gt; &gt;     &gt; ./install.sh<br>
&gt; &gt;     &gt; ./fuego-host-scripts/docker-<wbr>remove-container.sh<br>
&gt; &gt;     &gt; ./fuego-host-scripts/docker-<wbr>create-container.sh<br>
&gt; &gt;     &gt; ./fuego-host-scripts/docker-<wbr>start-container.sh<br>
&gt; &gt;     &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;     The build worked.<br>
&gt; &gt;<br>
&gt; &gt;     &gt; In fuego:<br>
&gt; &gt;     &gt; ftc add-nodes fuego-test<br>
&gt; &gt;     &gt; ftc add-jobs -b fuego-test -t Functional.fuegotest<br>
&gt; &gt;<br>
&gt; &gt;     these worked.<br>
&gt; &gt;<br>
&gt; &gt;     &gt; Then you will be able to start the test through Jenkins and see the<br>
&gt; &gt; results.<br>
&gt; &gt;     Running the test in jenkins resulted in the log that&#39;s attached.<br>
&gt; &gt;<br>
&gt; &gt;      -- Tim<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt;<br>
</div></div>&gt; ______________________________<wbr>_________________<br>
&gt; Fuego mailing list<br>
&gt; <a href="mailto:Fuego@lists.linuxfoundation.org">Fuego@lists.linuxfoundation.<wbr>org</a><br>
&gt; <a href="https://lists.linuxfoundation.org/mailman/listinfo/fuego" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/fuego</a><br>
</blockquote></div><br></div>