Running docker images behind proxy (i.e., corporate network or non-open network) might fail onboarding due to non reachability to internet for few scenarios.

[KiranSukhavasi]

Issue: When SDO AIO or any other docker container is running behind the proxy and needs to verify the epid while onboarding sdo client devices then it might fail to reach internet due to few proxy settings not updated in the Dockerfile and docker environment can't reach outside the network.

Solution:
For example: in the case of AIO, the files Dockerfile and Dockerfile.rendezvous needs to be updated with the below flags and build the docker again so that it can reach the outside network using these proxy settings.**

ENV http_proxy http://<proxy.domain.com>:<port>
ENV https_proxy http://<proxy.domain.com>:<port>
ENV no_proxy <domain.com>,<.domain.com>,.localdomain,localhost,127.0.0.1
ENV _JAVA_OPTIONS -Dhttp.proxyHost=<proxy.domain.com> -Dhttp.proxyPort=<port> -Dhttps.proxyHost=<proxy.domain.com> -Dhttps.proxyPort=<port>