Proxy settings are ignored
See original GitHub issueDescription
Since Docker 17.07 you can configure the client to use a proxy. When running build via d-m-p it doesn’t work.
See linked project on how to reproduce.
Info
- d-m-p version : 0.27.2
- Maven version (
mvn -v
) : 3.5.4 - Docker version : 18.06.1-ce
- Sample project : https://github.com/jakub-bochenski/demp-link-problem/tree/proxy
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
An HTTP proxy is ignored when RPC calls are made from a ...
Fixes a problem in which an HTTP proxy is ignored when RPC calls are made from a computer that is running Windows 8.1,...
Read more >'Ignore Proxy Settings' in the Web Security Service portal isn't ...
'Ignore Proxy Settings' does not make the user traffic ignore the proxy settings that are configured on the browsers.
Read more >Network proxy settings is ignored. - Apple Support Communities
I need a proxy for some content filtering enabled on my computer, so I've setup a proxy in Network preferences.
Read more >Proxy settings are ignored when trying to activate the product
IntelliJ IDEA Ultimate 2017.3.2 ignores proxy settings when trying to activate it with a JetBrains account. I ran a wireshark session and I...
Read more >Proxy Settings ignored · Issue #1362 · scalameta/metals · GitHub
I am behind a proxy (no login necessary) and the Visual Studio Code extension doesn't seem to use the correct proxy although it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
same problem proxy set in ~/.docker/config.json is ignored
plugin version 0.26.0 docker 18.06.1-ce
thanks @jakub-bochenski for the workaround 😃
I totally agree that a proxy setting should not be part of the build (i.e. not entered in the pom.xml) and ideally not how the build is called. So it should be specific to the environment where the build is called.
So I agree and I think respecting the proxy settings in ~/.docker/config.json is a good thing.
@jakub-bochenski @rohanKanojia fancy for jumping on a PR for this ? (sorry, no space left on my plate right now 😭