How do you run apt-get in a dockerfile behind a proxy

Question

I am running a virtual machine  Ubuntu 13 10  with docker  version 0 8 1  build a1598d1    I am trying to build an image with a dockerfile   First  I want to update the packages  using the code below - the proxy is obfuscated  but apt-get times out with the error  Could not resolve  archive ubuntu com    FROM ubuntu 13 10 ENV HTTP PROXY  lt HTTP PROXY gt  ENV HTTPS PROXY  lt HTTPS PROXY gt  RUN export http proxy  HTTP PROXY RUN export https proxy  HTTPS PROXY RUN apt-get update  amp  amp  apt-get upgrade   I have also run the following in the host system   sudo HTTP PROXY http    lt PROXY DETAILS gt   docker -d  amp    The host is able to run apt-get without issue   How can I change the dockerfile to allow it to reach the ubuntu servers from within the container   Update  I ran the code in CentOS  changing the FROM ubuntu 13 10 to FROM centos  and it worked fine   It seems to be a problem with Ubuntu

User · Answer

UPDATE   You have wrong capitalization of environment variables in ENV  Correct one is http proxy  Your example should be   FROM ubuntu 13 10 ENV http proxy  lt HTTP PROXY gt  ENV https proxy  lt HTTPS PROXY gt  RUN apt-get update  amp  amp  apt-get upgrade   or  FROM centos ENV http proxy  lt HTTP PROXY gt  ENV https proxy  lt HTTPS PROXY gt  RUN yum update    All variables specified in ENV are prepended to every RUN command  Every RUN command is executed in own container environment  so it does not inherit variables from previous RUN commands   Note  There is no need to call docker daemon with proxy for this to work  although if you want to pull images etc  you need to set the proxy for docker deamon too  You can set proxy for daemon in  etc default docker in Ubuntu  it does not affect containers setting      Also  this can happen in case you run your proxy on host  i e  localhost  127 0 0 1   Localhost on host differ from localhost in container  In such case  you need to use another IP  like 172 17 42 1  to bind your proxy to or if you bind to 0 0 0 0  you can use 172 17 42 1 instead of 127 0 0 1 for connection from container during docker build   You can also look for an example here  How to rebuild dockerfile quick by using cache

User · Answer

As suggested by other answers  --build-arg may be the solution  In my case  I had to add --network host in addition to the --build-arg options   docker build -t  lt TARGET gt  --build-arg http proxy http    lt IP PORT gt  --build-arg https proxy http    lt IP PORT gt  --network host

User · Answer

Use --build-arg in lower case environment variable   docker build --build-arg http proxy http   proxy port  --build-arg https proxy http   proxy port  --build-arg ftp proxy http   proxy port --build-arg no proxy localhost 127 0 0 1 company com -q false

User · Answer

You can use the --build-arg option when you want to build using a Dockerfile   From a link on https   github com docker docker issues 14634   see the section  Build with --build-arg with multiple HTTP PROXY     root pppdc9prda2y java   docker build    --build-arg https proxy  HTTP PROXY --build-arg http proxy  HTTP PROXY    --build-arg HTTP PROXY  HTTP PROXY --build-arg HTTPS PROXY  HTTP PROXY    --build-arg NO PROXY  NO PROXY  --build-arg no proxy  NO PROXY -t java     NOTE  On your own system  make sure you have set the HTTP PROXY and NO PROXY environment variables

User · Answer

and If you want to set proxy for wget you should put these line in your Dockerfile   ENV http proxy YOUR-PROXY-IP PORT  ENV https proxy YOUR-PROXY-IP PORT  ENV all proxy YOUR-PROXY-IP PORT

User · Answer

Updated on 02 10 2018  With new feature in docker option --config  you needn t set Proxy in Dockerfile any more  You can have same Dockerfile to be used in and out corporate environment   --config string      Location of client config files  default     docker     or environment variable DOCKER CONFIG   DOCKER CONFIG  The location of your client configuration files     export DOCKER CONFIG    docker   https   docs docker com engine reference commandline cli   https   docs docker com network proxy   I recommend to set proxy with httpProxy  httpsProxy  ftpProxy and noProxy  The official document misses the variable ftpProxy which is useful sometimes       proxies          default              httpProxy    http   127 0 0 1 3001         httpsProxy    http   127 0 0 1 3001          ftpProxy    http   127 0 0 1 3001         noProxy      test example com  example2 com              Adjust proxy IP and port if needed and save to    docker config json  After yo set properly with it  you can run docker build and docker run as normal     docker build -t demo       docker run -ti --rm demo env grep -ri proxy  standard input  http proxy http   127 0 0 1 3001  standard input  HTTPS PROXY http   127 0 0 1 3001  standard input  https proxy http   127 0 0 1 3001  standard input  NO PROXY   test example com  example2 com  standard input  no proxy   test example com  example2 com  standard input  FTP PROXY http   127 0 0 1 3001  standard input  ftp proxy http   127 0 0 1 3001  standard input  HTTP PROXY http   127 0 0 1 3001   Old answer  Decommissioned   Below setting in Dockerfile works for me  I tested in CoreOS  Vagrant and boot2docker  Suppose the proxy port is 3128  In Centos   ENV http proxy ip 3128  ENV https proxy ip 3128   In Ubuntu   ENV http proxy  http   ip 3128  ENV https proxy  http   ip 3128    Be careful of the format  some have http in it  some haven t  some with single quota  if the IP address is 192 168 0 193  then the setting will be   In Centos   ENV http proxy 192 168 0 193 3128  ENV https proxy 192 168 0 193 3128   In Ubuntu   ENV http proxy  http   192 168 0 193 3128  ENV https proxy  http   192 168 0 193 3128    If you need set proxy in coreos  for example to pull the image  cat  etc systemd system docker service d http-proxy conf   Service  Environment  HTTP PROXY http   192 168 0 193 3128

User · Answer

i had the same problem and found another little workaround  i have a provisioner script that is added form the docker build environment  In the script i set the environment variable dependent on a ping check   Dockerfile   ADD script sh  tmp script sh RUN  tmp script sh   script sh   if ping -c 1 ix de   then     echo  direct internet doing nothing  else     echo  proxy environment detected setting proxy      export http proxy  lt proxy address gt  fi   this is still somewhat crude but worked for me

User · Answer

We are doing      ENV http proxy http   9 9 9 9 9999 ENV https proxy http   9 9 9 9 9999   and at end of dockerfile      ENV http proxy    ENV https proxy      This  for now  until docker introduces build env vars   allows the proxy env vars to be used for the build ONLY without exposing them  The alternative to solution is NOT to build your images locally behind a proxy but to let docker build your images for you using docker  automated builds   Since docker is not building the images behind your proxy the problem is solved  An example of an automated build is available at      https   github com danday74 docker-nginx-lua  GITHUB repo   https   registry hub docker com u danday74 nginx-lua  DOCKER repo which is watching the github repo using an automated build and doing a docker build on a push to the github master branch

User · Answer

before any apt-get command in your Dockerfile you should put this line   COPY apt conf  etc apt apt conf   Dont f forget to  create apt conf in the same folder that you have the Dockerfile  the content of the apt conf file should be like this   Acquire  socks  proxy  socks   YOUR-PROXY-IP PORT    Acquire  http  proxy  http   YOUR-PROXY-IP PORT    Acquire  https  proxy  http   YOUR-PROXY-IP PORT      if you use username and password to connect to your proxy then the apt conf should be like as below   Acquire  socks  proxy  socks   USERNAME PASSWORD YOUR-PROXY-IP PORT    Acquire  http  proxy  http   USERNAME PASSWORD YOUR-PROXY-IP PORT    Acquire  https  proxy  http   USERNAME PASSWORD YOUR-PROXY-IP PORT      for example    Acquire  https  proxy  http   foo bar 127 0 0 1 8080      Where the foo is the username and bar is the password

User · Answer

As Tim Potter pointed out  setting proxy in dockerfile is horrible  When building the image  you add proxy for your corporate network but you may be deploying in cloud or a DMZ where there is no need for proxy or the proxy server is different    Also  you cannot share your image with others outside your corporate n w

User · Answer

A slight alternative to the answer provided by  Reza Farshi  which works better in my case  is to write the proxy settings out to  etc apt apt conf using echo via the Dockerfile e g    FROM ubuntu 16 04  RUN echo  Acquire  http  proxy    HTTP PROXY    nAcquire  https  proxy    HTTPS PROXY      gt   etc apt apt conf    Test that we can now retrieve packages via  apt-get  RUN apt-get update   The advantage of this approach is that the proxy addresses can be passed in dynamically at image build time  rather than having to copy the settings file over from the host    e g   docker build --build-arg HTTP PROXY http    lt host gt   lt port gt  --build-arg HTTPS PROXY http    lt host gt   lt port gt     as per docker build docs

User · Answer

If you have the proxies set up correctly  and still cannot reach the internet  it could be the DNS resolution  Check  etc resolve conf on the host Ubuntu VM  If it contains nameserver 127 0 1 1  that is wrong   Run these commands on the host Ubuntu VM to fix it   sudo vi  etc NetworkManager NetworkManager conf   Comment out the line  dns dnsmasq  with a        restart the network manager service sudo systemctl restart network-manager  cat  etc resolv conf   Now  etc resolv conf should have a valid value for nameserver  which will be copied by the docker containers

[docker] How do you run `apt-get` in a dockerfile behind a proxy?

Examples related to docker

Examples related to apt

Examples related to http-proxy