Is your feature request related to a problem? Please describe.
Starting Toolbox from a corporate network that blocks internet access for any path that does not use corporate HTTP Proxies (such as Squid or any other type of HTTP proxy that inspects packets) is not trivially possible.
Describe the solution you'd like
I would love if Toolbox had a way to configure a HTTP proxy globally or per user which the init script would then use to configure that proxy for the package managers inside of the containers. For example in Ubuntu/Debian, adding a file /etc/apt/apt.conf.d/99-toolbxproxy containing:
Acquire::http::Proxy "http://username:password@yourproxyaddress:proxyport";
Acquire::https::Proxy "http://username:password@yourproxyaddress:proxyport";
Describe alternatives you've considered
For some container OS's it might be enough to have HTTPS_PROXY https_proxy HTTP_PROXY http_proxy NO_PROXY and no_proxy environment variables set.
I've used the Github search function to check for similar issues, but I didn't find any.
Is your feature request related to a problem? Please describe.
Starting Toolbox from a corporate network that blocks internet access for any path that does not use corporate HTTP Proxies (such as Squid or any other type of HTTP proxy that inspects packets) is not trivially possible.
Describe the solution you'd like
I would love if Toolbox had a way to configure a HTTP proxy globally or per user which the
initscript would then use to configure that proxy for the package managers inside of the containers. For example in Ubuntu/Debian, adding a file/etc/apt/apt.conf.d/99-toolbxproxycontaining:Describe alternatives you've considered
For some container OS's it might be enough to have
HTTPS_PROXYhttps_proxyHTTP_PROXYhttp_proxyNO_PROXYandno_proxyenvironment variables set.I've used the Github search function to check for similar issues, but I didn't find any.