Example of using an upstream proxy which requires authentication missing

[muelli]

I would like to use docker behind a corporate, authenticating firewall.

It is not clear to me how to achieve that.
I've tried to use cache_peer proxy.acme.corp parent 8080 0 no-query default login=user:pass, but that fails with temporary disabling (Bad Gateway) digest from proxy.acme.corp.

Also, it logs ERROR: No forward-proxy ports configured.

[dev1x]

I have this working properly, you need to be sure that your corporate firewall is compatible with one of these authentication protocols
http://wiki.squid-cache.org/Features/Authentication

[joshq00]

@WISCAS it would be helpful if you shared how you've successfully configured

[angelcervera]

@dev1x Please, could you share your configuration or explain how to do it?

[silarsis]

There are a few pages around on how to do squid behind a corporate proxy - http://www.christianschenk.org/blog/using-a-parent-proxy-with-squid/ is a good reference, and mentions use of no-digest. From the error for the first poster, it looks like your corporate proxy may not be squid, and thus trying to use digests is failing.

I'm not currently using this project behind another proxy like that, so I'm not able to provide a simple config to fix - and I suspect it may be different from proxy to proxy anyway. Likely various of the options (no-cache, no-digest, login=, etc) may need to be pieced together to make it work with whatever your flavour of proxy is.

If people provide working configurations, I'm happy to add them to the readme / config files as guides for people with the same corporate proxies.