[caasp-beta] CaaS 1.0 beta2 pods issues with behind proxy server
Robert Roland
robert.roland at suse.com
Wed May 3 10:50:56 MDT 2017
The systemd unit for Docker contains:
[Service]
EnvironmentFile=/etc/sysconfig/docker
So, setting:
HTTP_PROXY=...
HTTPS_PROXY=...
NO_PROXY=...
inside /etc/sysconfig/docker should be sufficient to configure the
proxies. You shouldn't need additional systemd drop-in files.
On 05/03/2017 03:54 AM, Alvaro Saurin wrote:
>
> Hi Robert,
>
> Sorry but I don't understand the relation between /etc/default/docker
> and the HTTP_PROXY environment variable. Could you give more details?
>
> Cheers
>
>
> Alvaro
>
>
>
> On 04/28/2017 06:09 PM, Robert Roland wrote:
>> That shouldn't be necessary because our default Docker systemd uses
>> /etc/default/docker as an EnvironmentFile?
>>
>>
>> On April 28, 2017 2:19:17 AM PDT, "Miquel Sabaté Solà"
>> <msabate at suse.com> wrote:
>>
>> Hello,
>>
>> I've just opened a ticket in our internal bugzilla. We are
>> tracking this issue internally and working on it. That being said,
>> to make it work manually you should follow this steps:
>>
>> 1. ssh to each machine in the cluster
>>
>> 2. create a systemd drop-in directory for the docker service:
>>
>> $ mkdir /etc/systemd/system/docker.service.d
>>
>> 3. create a file called
>> /etc/systemd/system/docker.service.d/http-proxy.conf that adds the
>> HTTP_PROXY environment variable:
>>
>> [Service]
>> Environment="HTTP_PROXY=http://proxy.example.com:80/"
>>
>> 4. flush changes:
>>
>> $ sudo systemctl daemon-reload
>>
>> 5. verify that the configuration has been loaded:
>>
>> $ sudo systemctl show --property Environment docker
>> Environment=HTTP_PROXY=http://proxy.example.com:80/
>>
>> 6. restart Docker:
>>
>> $ sudo systemctl restart docker
>>
>> In the future we should ask the user about proxies in some
>> "advanced configuration" option in YaST, pass it to the worker
>> nodes through the autoyast.xml and set automatically the
>> HTTP_PROXY for docker.
>>
>> Cheers,
>>
>> Ns @ 2017-04-27 15:20 GMT:
>>
>> Hi Flavio, Yes I got information from Robert, however it
>> wasn’t working …? Best Regards, Rushi. I MAY BE ONLY ONE
>> PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE On
>> 4/27/17, 4:49 PM, "caasp-beta-bounces at lists.suse.com on
>> behalf of Flavio Castelli" <caasp-beta-bounces at lists.suse.com
>> on behalf of fcastelli at suse.com> wrote: On 04/26/2017 06:09
>> AM, Ns, Rushi wrote:
>>
>> As you mentioned you should try to provide that
>> information during the installation or some sort of
>> post-steps as all most all enterprise customers have
>> proxy to go internet.
>>
>> You are right, this is definitely something we should provide
>> either during the installation time or when deploying the
>> cluster from the web UI. I think Robert pointed you in the
>> right direction, please let us know if the proposed solution
>> is not working. Thanks for your feedback. Cheers Flavio
>> ------------------------------------------------------------------------
>> caasp-beta mailing list caasp-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/caasp-beta
>> ------------------------------------------------------------------------
>> caasp-beta mailing list caasp-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/caasp-beta
>>
>>
>>
>> --
>> Miquel Sabaté Solà,
>> PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565
>>
>> _______________________________________________
>> caasp-beta mailing list
>> caasp-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/caasp-beta
> --
> Alvaro Saurin<alvaro.saurin at suse.com>
> Senior Software Engineer
> SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755;https://www.suse.com/
> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170503/8960e595/attachment.htm>
More information about the caasp-beta
mailing list