Closed rahul-amaram-vizury closed 9 years ago
I think this is caused by needing to set the proxy config in /etc/systemd/system/docker.service.d/http-proxy.conf on the newer deb/ubuntu versions which use systemd instead of upstart.
I've managed to get docker respecting the proxy by manually adding that file with content like:
[Service]
Environment="HTTP_PROXY=http://10.0.0.10:8080/" "HTTPS_PROXY=http://10.0.0.10:8080/"
... however I don't know Ruby so my attempts to update vagrant-proxyconf to push this out have been unsuccessful so far.
I've made a pull request #133 which may address this, it works for me but as I say I'm not an experienced Ruby person so I may have made some fundamental errors in it!
@rahul-amaram-vizury I am sorry, I could not respond. Please tell me the Debian version. @mrsheepuk Thank you for reminding me, I will check it later.
I don't remember the complete context for this ticket as it has been a long time. I am currently using Debian Testing (stretch). I think I had implemented some workaround for this problem but I'm sorry I cannot recollect it now.
OK. Ubuntu/Debian Docker official package issue is discussed on #133. So I have closed this issue.
Is this resolved because having ubuntu 18.04 as guest i still have to manually change it like here: https://docs.docker.com/config/daemon/systemd/#httphttps-proxy
Here is the configuration:
Is anything else needed? When I run vagrant using --debug , it shows that the proxyconf plugin got loaded. However, the proxy configuration does not seem to be used by docker. I believe I also restarted docker though I am not sure if this is really needed.