I have a Juju setup with local LXC provider in our office environment - which requires an explicit proxy setting to access Internet - http/https/ftp proxy settings ...(http://xx.yy.zz.aa:8000/). I have set these for apt-get in /etc/apt/apt.conf as well as as environment variables #export http_proxy=<proxy>, export https_proxy=<proxy>, export ftp_proxy=<proxy>(tried both with local ~/.bashrc and global in /etc). I also had to explicitly set this separately in ~/.curlrc and /etc/wgetrc for them to work correctly when things get spawned - they don't seem to take it from the env variables. The biggest issue though seems to be that most charms start off the install hook with add-apt-repository xxxx in the lxc instance and the charm just gets stuck unable to get past the proxy. The work around for me has been to download the charm locally, edit the install hook and add these http/s proxies in their and deploy the charm. In this case, the charm continues and downloads all the relevant things. So, my question is - is there a common place to set or specify proxies when deploying charms for lxc provider. How to update the LXC instance's /etc/apt/apt.conf and env variables with http/s proxy settings.
I have googled and searched launchpad, but haven't been able to get the answers. Appreciate any assistance.
Regards
Just a quick correction and some more info...I actually meant to say that the LXC instance's apt configuration gets configured correctly with the proxy setting, but NOT the env variables. So, any charm that actually just has apt-get install .... works fine directly without me having to download it locally and editing. Those charms that have add-apt-repository get stuck since pycurl doesn't seem to know how to get to any proxies and tried to connect to the servers directly (verified with wireshark) and fails. Editing the install hook, adding the proxy and redeploying as local charm works.