<html><head></head><body>That shouldn't be necessary because our default Docker systemd uses /etc/default/docker as an EnvironmentFile?<br>
<br><br><div class="gmail_quote">On April 28, 2017 2:19:17 AM PDT, "Miquel Sabaté Solà" <msabate@suse.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hello,<br /><br />I've just opened a ticket in our internal bugzilla. We are <br />tracking this issue internally and working on it. That being said, <br />to make it work manually you should follow this steps:<br /><br />1. ssh to each machine in the cluster<br /><br />2. create a systemd drop-in directory for the docker service:<br /><br /> $ mkdir /etc/systemd/system/docker.service.d<br /><br />3. create a file called <br />/etc/systemd/system/docker.service.d/http-proxy.conf that adds the <br />HTTP_PROXY environment variable:<br /><br /> [Service]<br /> Environment="HTTP_PROXY=<a href="http://proxy.example.com:80">http://proxy.example.com:80</a>/"<br /><br />4. flush changes:<br /><br /> $ sudo systemctl daemon-reload<br /><br />5. verify that the configuration has been loaded:<br /><br /> $ sudo systemctl show --property Environment docker<br /> Environment=HTTP_PROXY=<a href="http://proxy.example.com:80">http://proxy.example.com:80</a>/<br /><br />6. restart Docker:<br /><br /> $ sudo systemctl restart docker<br /><br />In the future we should ask the user about proxies in some <br />"advanced configuration" option in YaST, pass it to the worker <br />nodes through the autoyast.xml and set automatically the <br />HTTP_PROXY for docker.<br /><br />Cheers,<br /><br />Ns @ 2017-04-27 15:20 GMT:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Hi Flavio,<br /><br /> Yes I got information from Robert, however it wasn’t working …?<br /><br /><br /> Best Regards,<br /><br /> Rushi.<br /> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A <br /> DIFFERENCE<br /><br /><br /> On 4/27/17, 4:49 PM, "caasp-beta-bounces@lists.suse.com on <br /> behalf of Flavio Castelli" <caasp-beta-bounces@lists.suse.com on <br /> behalf of fcastelli@suse.com> wrote:<br /><br /> On 04/26/2017 06:09 AM, Ns, Rushi wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> As you mentioned you should try to provide that <br /> information during the installation or some sort of <br /> post-steps as all most all enterprise customers have proxy <br /> to go internet.<br /></blockquote><br /> You are right, this is definitely something we should <br /> provide either<br /> during the installation time or when deploying the cluster <br /> from the web UI.<br /><br /> I think Robert pointed you in the right direction, please <br /> let us know if<br /> the proposed solution is not working.<br /><br /> Thanks for your feedback.<br /><br /> Cheers<br /> Flavio<br /><hr /><br /> caasp-beta mailing list<br /> caasp-beta@lists.suse.com<br /> <a href="http://lists.suse.com/mailman/listinfo/caasp-beta">http://lists.suse.com/mailman/listinfo/caasp-beta</a><br /><br /><br /><hr /><br /> caasp-beta mailing list<br /> caasp-beta@lists.suse.com<br /> <a href="http://lists.suse.com/mailman/listinfo/caasp-beta">http://lists.suse.com/mailman/listinfo/caasp-beta</a><br /></blockquote><br /><br />--<br />Miquel Sabaté Solà,<br />PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565<br /></pre></blockquote></div></body></html>