Open suxlv2 opened 1 year ago
@suxlv2 Feature Utility doesn't support no_proxy
currently but it looks like there is an issue already tracking that here https://github.com/OpenLiberty/open-liberty/issues/23684.
Unless you are able to use your local network (i.e. build with
Edit: looks like FEATURE_REPO_URL won't support this type of reverse proxy approach as you aren't able to access https://repo.maven.apache.org/maven2/ --network=host
) that proxies to your local Maven repo on your host or connect to a manually created network that proxies to your local Maven repo within a container, it may not be currently possible.
Could you please elaborate a bit more on the need for the no_proxy
flag?
@suxlv2 Are you still facing this problem? If so, please provide answers to the above questions raised by @kabicin. Thank you.
no_proxy isn't used or just ignored.
Using
open-liberty:23.0.0.6-kernel-slim-java11-openj9-ubi
.The problem: (
features.sh
) Regardless of the existing proxy settings, script reports, that it can not access my local maven repository. Tried dozens of combinations: with & w/o ENV _httpproxy & _httpsproxy & _noproxy values in Dockerfile. With & w/o proxy set infeatureUtility.properties
&repositories.properties
.All I see in the log is just:
Clarification: https://repo.maven.apache.org/maven2/ is blocked in my network, so the log message seems to be OK. Even with proxy this one isn't allowed in our network.
Dockerfile
(removed/masked few lines)Clarification: The
app.war
was built in the same VM (fetched artifacts from the maven repo just fine), right before running the docker build.Server.xml
(features part)fetureUtility.properties
repositories.properties