Http proxies and beta 15

The beta 15 release notes state: “New Settings menu to configure http proxies”.
But I can’t manage to find it…

Thanks,
–nick

1 Like

Oops, we were planning to have that ready, but it wasn’t and we forgot to update that part of the release notes. Hopefully it’ll be ready for one of the next betas
Rolf

1 Like

OK. Can I use env variables to set the http(s) proxy or must I go back to docker toolbox? (cannot test @home)

Thanks,
–nick

1 Like

Any answer? is there a workaround to set the env variable manually in the docker host that docker for windows runs?

Is that also planned for Docker for Mac ?
In my company we have an auto-configuring proxy through a .pac file, and this doesn’t seem to work with docker.

It would be nice to be able to define a proxy (and certificates as well)

It’s absolutely planned for Mac too!

Still not in beta16, is there plans to get it in beta17? Can we follow that anywhere? It will be a big boost for our developer environment :slight_smile:

Unfortunately, due to last minute glitch this did not made the cut for beta17.
This should be in beta18, expect it next week.

1 Like

great to see this, but: It seems to, that implicit setting of proxies are inherited from OS settings (which is great) are far way slower removed (as it turns out for me: Switching Network Environment + restarting docker (yes, with the VM) doesn’t help, but proxy settings are pruned / auto-set after closing the lid and continue work from sleep?!?! Can anyone confirm this? OR should any environment change automatically be applied “at instant” to docker?

P.S: what is the meaning of proxy settings grayed out as background in the input fields? Inherited from OS? Looks like some “enter example.com here” and you have no choice to manually “prune” them?! Perhaps this would be a great enhancement?