From afb7afdaaca01cc3b8a2cf17b5fc9c8a5af016b0 Mon Sep 17 00:00:00 2001 From: astiphout Date: Fri, 12 Jan 2018 10:44:59 +0100 Subject: [PATCH] additional comment regarding ENV http_proxy It took me a while to figure out that ENV settings are also used during execution, so these must be cleared otherwise inter-container traffic also hits the proxy! --- docs/install.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/install.rst b/docs/install.rst index 03aee1c..1aaac8a 100644 --- a/docs/install.rst +++ b/docs/install.rst @@ -33,7 +33,7 @@ OpenNTI is available on DockerCloud_ and this project provide scripts to easily .. NOTE:: - On Ubuntu, you'll have to add "sudo" before the last command - - In case of have internet access through a proxy, before executing 'make start', edit all Dockeriles (those in the main directory and in the plugins directory), and include the lines ENV http_proxy and ENV https_proxy + - In case of have internet access through a proxy, before executing 'make start', edit all Dockerfiles (those in the main directory and in the plugins directory), and include the lines ENV http_proxy and ENV https_proxy . Be sure to clear these environment settings at the Dockerfile but before the final CMD using: ENV http_proxy "" and ENV https_proxy "". The ENV settings are used for both build and execution: without clearing these, it will prevent connectivity between containers (172.17.0.0/16). By default it will start 3 containers and it's working in **non-persistent mode**, once you stop it all data are gone. It's possible to start the main container in **persistent mode** to save the database outside the container, b