[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[che-dev] WARN: We have identified that http and https proxies are set but no_proxy is not. This may cause fatal networking errors. Set no_proxy for your Docker daemon!
|
Hi there!
I recently upgrade my version of Docker for Mac to 18.03.0-ce-mac60 (23751) and I am now receiving a warning about my HTTP_PROXY set-up.
I have googled and I found that there was an issue/change introduced in a 17. release of Docker for Mac. However, people are suggesting that there is no longer an issue.
I was wondering if anyone on the Che mailing list had seen similar, encountered any issues because of the PROXY settings and what they did to correct any problems.
Thank you for your tremendous support as usual!
Andrew
< my command line for starting Che and the warning message >
+ ip=10.37.34.57
+ docker run -it --rm --name run-che -e CHE_HOST=10.37.34.57 -e CHE_DOCKER_IP_EXTERNAL=10.37.34.57 -v /var/run/docker.sock:/var/run/docker.sock -v /Users/amclach/Work/GitHub/cheData:/data -v /Users/amclach/Work/GitHub/che-assembly/assembly-che/assembly-main/target/eclipse-che-5.22.0/eclipse-che-5.22.0:/assembly eclipse/che:latest start --skip:nightly
WARN: Bound 'eclipse/che' to 'eclipse/che:5.22.1'
INFO: Proxy: HTTP_PROXY=docker.for.mac.http.internal:3128, HTTPS_PROXY=docker.for.mac.http.internal:3129, NO_PROXY=
WARN: Potential networking issue discovered!
WARN: We have identified that http and https proxies are set but no_proxy is not. This may cause fatal networking errors. Set no_proxy for your Docker daemon!
