Working with snappy behind a ntlm proxy
josephwinston at mac.com
Mon Jan 26 23:57:40 UTC 2015
My use cases include developing in snapping and then deploying to snappy.
The environment variables http_proxy and https_proxy, appear to work as
expected in my ntlm world.
I'll now need a way to provision snappy so that the developers don't
have to worry about the proxy.
On 1/26/2015 6:07 AM, Alexander Sack wrote:
> do you want to make a snappy product that works in ntlm enabled
> networks or for development purpose?
> For the latter, maybe having such cntlm proxy on your host machine
> would be good enough to get you going?
> I just tried setting up network-manager ethernet connection that is
> "shared to other computers" and then I could get an IP from my ubuntu
> host; guess if i had a proxy on that host now I could us http_proxy
> etc. envs to make it work...
> mvo: can you confirm that those proxy envs are supported by snappy tool?
> - Alexander
> On Sat, Jan 24, 2015 at 7:08 PM, Joseph Winston <josephwinston at mac.com> wrote:
>> At work, I must live behind a ntlm proxy and in the past I used some
>> combination of cntlm (http://cntlm.sourceforge.net/) and adding HTTP_PROXY
>> and HTTPS_PROXY entries to the Dockerfiles. And if I was using vagrant, I
>> added https://github.com/tmatilai/vagrant-proxyconf entries to my
>> What is the recommend workflow for using snappy in an environment that
>> requires ntlm?
>> snappy-devel mailing list
>> snappy-devel at lists.ubuntu.com
>> Modify settings or unsubscribe at:
More information about the snappy-devel