Same problem here. I've found that https://access.redhat.com/solutions/2338971 to workaround
Best Regards, Nicolas Dordet Consultant Middleware Red Hat <http://www.redhat.com> Consulting France Mobile : +33 (0)670413987 <https://mail.google.com/> On Mon, Feb 22, 2016 at 8:13 PM, Akram Ben Aissi <[email protected]> wrote: > Hamza > > The NO_PROXY variable does not accept subnets > Only individual ips or domain names. > > If the proxy replied that's an issue > > > On Monday, 22 February 2016, Mohamed Hamza Ben Mansour < > [email protected]> wrote: > >> Hi, >> >> Thank you both for your anwsers. >> >> @Akram, It is for the CDK/OSE installation registry. Yes I am setting the >> NO_PROXY for the subnet where the registry lies. In the build logs, when >> the builder tries to push to the registry, it is the corporate proxy who >> reponds with an HTML body and messages in French :) >> >> @Christian That is the sample plugin I used. It is is great for setting >> proxy conf for docker and the host but not for the container running OSE. >> >> The real question may be is how to set corporate proxy in a containerised >> installation ? >> >> Kind regards >> >> On Mon, Feb 22, 2016 at 5:22 PM, Christian Posta <[email protected]> >> wrote: >> >>> Can you try the proxy plugin? >>> >>> Vagrant.configure("2") do |config| >>> >>> if Vagrant.has_plugin?("vagrant-proxyconf") >>> >>> config.proxy.http = "http://us_proxy_foo:9000/ >>> <http://us_proxy_indy.xh1.lilly.com:9000/>" >>> >>> config.proxy.https = "http://us_proxy_foo:9000/ >>> <http://us_proxy_indy.xh1.lilly.com:9000/>" >>> >>> config.proxy.no_proxy = "localhost,127.0.0.1,.foo.com >>> <http://lilly.com/>" >>> >>> end >>> >>> end >>> >>> On Mon, Feb 22, 2016 at 6:31 AM, Mohamed Hamza Ben Mansour < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> I have a customer very intrested in running CDK on its windows boxes. >>>> While trying to run the Openshift flavoured Vagrantfile we encountred >>>> several problmes due to their corporate proxy. We used a Vagarant proxy >>>> plugin which configured docker and the host. We also added proxy >>>> information as env vars to the docker run instruction launching OSE. >>>> Nevertheless, we had another problem while pushing to the OSE registry : >>>> the proxy was denying it. Can you please advice on the best >>>> solution/configuration to adopt. >>>> >>>> Kind regards >>>> >>>> Have a question? >>>> First, check the FAQ: https://mojo.redhat.com/docs/DOC-943081 >>>> Next, check the archives: http://post-office.corp. >>>> redhat.com/archives/openshift-sme/ >>>> >>> >>> >>> >>> -- >>> *Christian Posta * >>> Principal Middleware Architect >>> twitter: @christianposta >>> >> >> > > -- > > Akram Ben Aissi Mob : +33 6 31 57 08 60 > Architect Cloud and Platform Mel : [email protected] > Red Hat Global Services Irc : akram > Twi : @ > <[email protected]>akrambenaissi > Red Hat France SARL http://www.redhat.fr > > > > Have a question? > First, check the FAQ: https://mojo.redhat.com/docs/DOC-943081 > Next, check the archives: http://post-office.corp. > redhat.com/archives/openshift-sme/ >
_______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
