Closed xasx closed 3 years ago
Have you tried the usual way of passing HTTP_PROXY
env variable to container?
I.e. start qodana like that:
docker run -e HTTP_PROXY=your.proxy.addr:3128 -e HTTPS_PROXY=your.proxy.addr:3128 ...
Yes, these are not respected.
I am going to try passing the -D proxy properties to idea64.vmoptions
Using gitlab ci, this did the trick to pick up the proxy env vars:
script:
- echo '-Djava.net.useSystemProxies=true' >> /opt/idea/bin/idea64.vmoptions
- /opt/idea/bin/entrypoint --results-dir=$CI_PROJECT_DIR/qodana --save-report --report-dir=$CI_PROJECT_DIR/qodana/report
Thank you for providing feedback and snippet of the solution! This issue would also help others.
Just a note that it is possible to pass java -D options also via env _JAVA_OPTIONS
or IDE_PROPERTIES_PROPERTY
:
https://github.com/JetBrains/Qodana/blob/main/Docker/techs.md#configuring
I am behind a corporate proxy and need Qodana to talk to it for internet access.
How to do that? Thanks.