Pass proxy settings to the DIND containers

sidoruka commented 4 years ago

Background At the moment, DIND containers configuration includes only registry credentials and a couple of driver settings. In certain environments, it is not possible to access external networks (e.g. for the packages installation) without the http(s)/no_proxy settings. So the users have to pass this manually using docker run -e http_proxy=... option.

Approach

Introduce a system preference launch.dind.container.vars (nullable, string) listing all the variables, which shall be passed to the DIND containers (if they are set for the host environment)
By default, the following variables shall be set for the launch.dind.container.vars preference: http_proxy,https_proxy,no_proxy,API,API_TOKEN
Introduce a system parameter (per run) CP_CAP_DIND_CONTAINER_NO_VARS, which disables this behavior

sidoruka commented 4 years ago

Backport to release/0.15

tcibinan commented 4 years ago

Backported to release/0.15 via 476f521aed3f308e1e8f30febae341385f32fe8c.

tcibinan commented 4 years ago

It will be also nice to have the same proxy parameters to be passed automatically during docker build call as well as docker run.

NShaforostov commented 4 years ago

Verified. Docs were updated via the #991

epam / cloud-pipeline

Pass proxy settings to the DIND containers #983