<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Bart and Tee,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To clarify the docker daemon proxy issue discussed in review comments[0], I move the discussion here for a clear view.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The question is, docker daemon proxy setting in starlingx is not the same as current docker doc[1]. The difference is we in starlingx only create http-proxy.conf for HTTP_PROXY, HTTPS_PROXY, NO_PROXY setting, while the document suggests
http-proxy.conf for HTTP_PROXY and https-proxy for HTTPS_PROXY. Does it impact the docker daemon proxy setting?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That might be a little confused of the terminology of above file name and environment variable name. HTTP_PROXY means all the target url requests go via this proxy server if the request type is http, and the same meaning as HTTPS_PROXY,
not the proxy server type itself is http or https. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Through my test of docker daemon proxy and golang net lib (used by docker daemon proxy connection) code[2] , the http-proxy.conf and https-proxy.conf have the same target just to set HTTP_PROXY/HTTPS_PROXY/NO_PROXY environment variables
to golang net lib. The file name of the conf does not impact the proxy setting. I even renamed http-proxy.conf to test.conf and got a successful pulling from http registry and both https registry through proxy. So I don’t think following current docker proxy
setting doc is a must.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Moreover, as I said in the review comments[0], starlingx docker daemon proxy setting was the official approach(only one http-proxy.conf file) at some time in 2018, but it’s disappeared. Some technical articles[3][4][5] indicates that this
setting approach is valid. Therefore, I think current starlingx approach for docker daemon proxy setting is valid and no changes needed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The remaining question from Tee to test https proxy is not the same as above. To use a https proxy server, the setting should be:<o:p></o:p></p>
<p class="MsoNormal">HTTP_PROXY=https://proxy.url:port<o:p></o:p></p>
<p class="MsoNormal">HTTPS_PROXY=https://proxy.url:port<o:p></o:p></p>
<p class="MsoNormal">No matter these environment variables are set in http-proxy.conf or https-proxy.conf or test.conf.<o:p></o:p></p>
<p class="MsoNormal">If test team has a https proxy server, this can be tested by current config mechanism.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[0] <a href="https://review.opendev.org/#/c/661825/">https://review.opendev.org/#/c/661825/</a><o:p></o:p></p>
<p class="MsoNormal">[1] <a href="https://docs.docker.com/config/daemon/systemd/#httphttps-proxy">
https://docs.docker.com/config/daemon/systemd/#httphttps-proxy</a><o:p></o:p></p>
<p class="MsoNormal">[2] <a href="https://github.com/golang/net/blob/master/http/httpproxy/proxy.go#L28">
https://github.com/golang/net/blob/master/http/httpproxy/proxy.go#L28</a><o:p></o:p></p>
<p class="MsoNormal">[3] <a href="https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.1.2/installing/install_proxy.html">
https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.1.2/installing/install_proxy.html</a><o:p></o:p></p>
<p class="MsoNormal">[4] <a href="https://elegantinfrastructure.com/docker/ultimate-guide-to-docker-http-proxy-configuration/">
https://elegantinfrastructure.com/docker/ultimate-guide-to-docker-http-proxy-configuration/</a><o:p></o:p></p>
<p class="MsoNormal">[5] <a href="https://www.thegeekdiary.com/how-to-configure-docker-to-use-proxy/">
https://www.thegeekdiary.com/how-to-configure-docker-to-use-proxy/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
<p class="MsoNormal">Mingyuan<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>