{"id":16745,"date":"2017-03-30T12:15:34","date_gmt":"2017-03-30T09:15:34","guid":{"rendered":"https:\/\/www.webcodegeeks.com\/?p=16745"},"modified":"2017-03-29T11:23:08","modified_gmt":"2017-03-29T08:23:08","slug":"using-docker-behind-proxy","status":"publish","type":"post","link":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/","title":{"rendered":"Using Docker Behind a Proxy"},"content":{"rendered":"

In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use Docker without direct internet access.<\/p>\n

By default, Docker assumes that the system running Docker and executing Docker commands has general access to the internet. Often in large corporate networks this is simply not the case. More often than not, a corporate network will route all internet traffic through a proxy.<\/p>\n

While this setup is generally transparent to the end user, this type of network environment often neglects command line tools such as Docker. For today\u2019s article, we will use Docker to build and run a simple container within a \u201clocked down\u201d network.<\/p>\n

A Simple Example of Working with a Proxy<\/h2>\n

In this article, we will be building a simple ubuntu<\/code>-based container that uses apt-get<\/code> to install curl<\/code>. While this example is simple, it will require us to leverage a proxy in several ways.<\/p>\n

Before jumping into the proxy settings however, let\u2019s take a quick look at the Dockerfile<\/code> we will be building from.<\/p>\n

FROM ubuntu\r\n\r\nRUN apt-get update && apt-get install -y curl<\/pre>\n
The above Dockerfile<\/code> only has two instructions: FROM<\/code>, which is used to specify which base image to build the container from, and RUN<\/code>. RUN<\/code> is used to execute commands, in this case apt-get<\/code> commands.<\/p>\n
Let\u2019s go ahead and attempt to execute a docker build<\/code> to see what happens by default in a \u201clocked down\u201d network.<\/p>\n
$ sudo docker build -t curl .\r\nSending build context to Docker daemon 12.29 kB\r\nSending build context to Docker daemon\r\nStep 0 : FROM ubuntu\r\nPulling repository ubuntu\r\nINFO[0002] Get https:\/\/index.docker.io\/v1\/repositories\/library\/ubuntu\/images: dial tcp 52.22.146.88:443: connection refused<\/pre>\n
From the above execution, we can see that the docker build<\/code> results in a download error of the base ubuntu<\/code> image. The reason is also pretty obvious: access to docker.io<\/code> was blocked.<\/p>\n
In order for this to work within our network, Docker will need to route its request through a proxy. This will allow Docker to indirectly communicate with docker.io<\/code>.<\/p>\n
Configuring Docker to Use a Proxy<\/h2>\n
On Ubuntu (which is the OS our Docker host is running), we can configure Docker to do this by simply editing the \/etc\/default\/docker<\/code> file.<\/p>\n
# If you need Docker to use an HTTP proxy, it can also be specified here.\r\n#export http_proxy=\"http:\/\/127.0.0.1:3128\/\"<\/pre>\n
Within the \/etc\/default\/docker<\/code> file, there is a line that is commented by default which specifies the http_proxy<\/code> environmental variable.<\/p>\n
In order to route Docker traffic through a proxy, we will need to uncomment this line and replace the default value with our proxy address.<\/p>\n
# If you need Docker to use an HTTP proxy, it can also be specified here.\r\nexport http_proxy=\"http:\/\/192.168.33.10:3128\/\"<\/pre>\n
In the above, we specify using the proxy located at 192.168.33.10:3128<\/code>. This proxy is a simple Squid<\/strong> proxy created using the sameersbn\/squid:3.3.8-23<\/code> Docker container.<\/p>\n
This proxy is not currently set up for username<\/strong>\u2013 or password<\/strong>-based authentication. However, if it was we could add those details using the https:\/\/username:password@192.168.33.10:3128\/<\/code> format.<\/p>\n
With changes made to \/etc\/default\/docker<\/code>, we need to restart the Docker service before our changes will take effect.<\/p>\n
We can do this by executing the service<\/code> command.<\/p>\n
# service docker restart\r\ndocker stop\/waiting\r\ndocker start\/running, process 32703<\/pre>\n
With our changes in effect, let\u2019s go ahead and see what happens when executing a docker build<\/code> command.<\/p>\n
$ sudo docker build -t curl .\r\nSending build context to Docker daemon 10.75 kB\r\nSending build context to Docker daemon\r\nStep 0 : FROM ubuntu\r\nlatest: Pulling from ubuntu\r\n2a2723a6e328: Pull complete\r\nfa1b78b7309e: Pull complete\r\n0ce8ddcea421: Pull complete\r\nc4cb212fd6fe: Pull complete\r\n109d5efde28a: Pull complete\r\n7f06d5cab2df: Pull complete\r\nDigest: sha256:f649e49c1ed34607912626a152efbc23238678af1ac37859b6223ef28e711a3f\r\nStatus: Downloaded newer image for ubuntu:latest\r\n ---> 7f06d5cab2df\r\nStep 1 : RUN apt-get update && apt-get install -y curl\r\n ---> Running in 39b964be90bc\r\nErr:1 http:\/\/archive.ubuntu.com\/ubuntu xenial InRelease\r\n  Cannot initiate the connection to archive.ubuntu.com:80 (2001:67c:1360:8001::17). - connect (101: Network is unreachable) [IP: 2001:67c:1360:8001::17 80]\r\nW: Failed to fetch http:\/\/archive.ubuntu.com\/ubuntu\/dists\/xenial\/InRelease  Cannot initiate the connection to archive.ubuntu.com:80 (2001:67c:1360:8001::17). - connect (101: Network is unreachable) [IP: 2001:67c:1360:8001::17 80]\r\nW: Some index files failed to download. They have been ignored, or old ones used instead.\r\nReading package lists...\r\nBuilding dependency tree...\r\nReading state information...\r\nE: Unable to locate package curl\r\nINFO[0013] The command [\/bin\/sh -c apt-get update && apt-get install -y curl] returned a non-zero code: 100<\/pre>\n
From the above build output, we can see that Docker was able to pull the ubuntu<\/code> image successfully. However, our build still failed due to connectivity issues.<\/p>\n
Specifically, our build failed during the apt-get<\/code> command execution.<\/p>\n
The reason the build failed is because even though we configured Docker itself to use a proxy, the operating environment within the container is not configured to use a proxy. This means when apt-get<\/code> was executed within the container, it attempted to go directly to the internet without routing through the proxy.<\/p>\n
In cases like this, it is important to remember that sometimes containers need to be treated in the same way we would treat any other system. The internal container environment works as if it is independent of the host system. That means configurations that exist on the host do not necessarily exist within the container. Our proxy is a prime example of that in practice.<\/p>\n
To that end, if we were to stand up a physical or virtual machine with Ubuntu installed in this network environment, we would need to configure apt-get<\/code> on that system to utilize a proxy. Just like we configured Docker to utilize a proxy.<\/p>\n
The same is true for the container we are building. Luckily, configuring a proxy for apt-get<\/code> is pretty easy.<\/p>\n
Configuring apt-get to Use a Proxy<\/h2>\n
We simply need to set the http_proxy<\/code> and https_proxy<\/code> environmental variables during build time. We can do this with the docker build<\/code> command itself.<\/p>\n
$ sudo docker build -t curl --build-arg http_proxy=http:\/\/192.168.33.10:3128 .<\/pre>\n
Or we can specify the http_proxy<\/code> value using the ENV<\/code> instruction within the Dockerfile<\/code>.<\/p>\n
FROM ubuntu\r\n\r\nENV http_proxy \"http:\/\/192.168.33.10:3128\"\r\nENV https_proxy \"http:\/\/192.168.33.10:3128\"\r\nRUN apt-get update && apt-get install -y curl<\/pre>\n
Both options are useful in different situations, but for this article we will specify the values within our Dockerfile<\/code>.<\/p>\n
Testing the proxy settings<\/h3>\n
With the http_proxy<\/code> and https_proxy<\/code> environmental variables added, let\u2019s rerun our build.<\/p>\n
$ sudo docker build -t curl .\r\nSending build context to Docker daemon 10.75 kB\r\nSending build context to Docker daemon\r\nStep 0 : FROM ubuntu\r\nlatest: Pulling from ubuntu\r\n2a2723a6e328: Pull complete\r\nfa1b78b7309e: Pull complete\r\n0ce8ddcea421: Pull complete\r\nc4cb212fd6fe: Pull complete\r\n109d5efde28a: Pull complete\r\n7f06d5cab2df: Pull complete\r\nDigest: sha256:f649e49c1ed34607912626a152efbc23238678af1ac37859b6223ef28e711a3f\r\nStatus: Downloaded newer image for ubuntu:latest\r\n ---> 7f06d5cab2df\r\nStep 1 : ENV http_proxy \"http:\/\/192.168.33.10:3128\"\r\n ---> Running in 6d66226a7cbf\r\n ---> 89fab90c9ca2\r\nRemoving intermediate container 6d66226a7cbf\r\nStep 2 : ENV https_proxy \"http:\/\/192.168.33.10:3128\"\r\n ---> Running in ce80b9502a59\r\n ---> c490a0c49b2b\r\nRemoving intermediate container ce80b9502a59\r\nStep 3 : RUN apt-get update && apt-get install -y curl\r\n ---> Running in 2eb328075f7e\r\nGet:1 http:\/\/archive.ubuntu.com\/ubuntu xenial InRelease [247 kB]\r\nGet:2 http:\/\/archive.ubuntu.com\/ubuntu xenial-updates InRelease [102 kB]\r\nGet:3 http:\/\/archive.ubuntu.com\/ubuntu xenial-security InRelease [102 kB]\r\nGet:4 http:\/\/archive.ubuntu.com\/ubuntu xenial\/main Sources [1103 kB]\r\nGet:5 http:\/\/archive.ubuntu.com\/ubuntu xenial\/restricted Sources [5179 B]<\/pre>\n
From the above, it appears our build was successful. Let\u2019s go ahead and run<\/code> this container.<\/p>\n
$ sudo docker run curl curl -v http:\/\/blog.codeship.com\r\n* Rebuilt URL to: http:\/\/blog.codeship.com\/\r\n*   Trying 192.168.33.10...\r\n> GET http:\/\/blog.codeship.com\/ HTTP\/1.1\r\n> Host: blog.codeship.com\r\n> User-Agent: curl\/7.47.0\r\n> Accept: *\/*\r\n> Proxy-Connection: Keep-Alive\r\n>\r\n< HTTP\/1.1 301 Moved Permanently\r\n< Server: nginx\r\n< Date: Wed, 22 Mar 2017 00:45:04 GMT\r\n< Content-Type: text\/html\r\n< Content-Length: 178\r\n< Location: https:\/\/blog.codeship.com\/<\/pre>\n
With the above curl<\/code> command output, we can see that our request to http:\/\/blog.codeship.com<\/code> was also proxied through the 192.168.33.10<\/code> proxy server. The reason for this is based on the way we specified the proxies within the container. The curl<\/code> command like apt-get<\/code>, uses the http_proxy<\/code> and https_proxy<\/code> environmental variables.<\/p>\n
It is important to remember that these values not only affect the container during build but also during execution. If for some reason we did not want to use this proxy during the execution of the container, we would need to reset the http_proxy<\/code> and https_proxy<\/code> values by either passing new values during docker run<\/code> execution or by changing our Dockerfile<\/code> to match the below.<\/p>\n
FROM ubuntu\r\n\r\nENV http_proxy \"http:\/\/192.168.33.10:3128\"\r\nENV https_proxy \"http:\/\/192.168.33.10:3128\"\r\nRUN apt-get update && apt-get install -y curl\r\nENV http_proxy \"\"\r\nENV https_proxy \"\"<\/pre>\n
With the above, when the container is launched with docker run<\/code>, the http_proxy<\/code> and https_proxy<\/code> values will be unset, allowing the container to route traffic without going through a proxy.<\/p>\n
Summary<\/h2>\n
In this article, we covered how to configure Docker (on Ubuntu<\/strong>) to use a proxy to download container images. We also explored how to configure apt-get<\/code> within the container to use a proxy and why it is necessary.<\/p>\n
While this is useful for Ubuntu laptops and hosts running Docker, many people use the Docker for Mac & Windows application. Luckily, the proxy configuration for Docker for Mac & Windows is pretty easy as well. In fact, it is part of the Docker preferences configuration.<\/p>\n
\"\"<\/a><\/p>\n
In the Docker preferences, there is an option for Proxies<\/em>. If you simply click this option, you can add both an HTTP<\/code> and HTTPS<\/code> proxy using the Manual proxy configuration<\/em> option.<\/p>\n
This setting will allow you to pull images from docker.io<\/code>, however, it does not replace configuring the proxy within the container. That step is required regardless of where the container is built<\/p>\n
\n\n\n\n
Reference: <\/span><\/td>\nUsing Docker Behind a Proxy<\/a> from our WCG partner<\/a>\u00a0Ben Cane at the Codeship Blog<\/a> blog.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use Docker without direct internet access. By default, Docker assumes that the system running Docker and executing Docker commands has general access to the internet. Often in large corporate …<\/p>\n","protected":false},"author":158,"featured_media":10356,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[217],"class_list":["post-16745","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","tag-docker"],"yoast_head":"\nUsing Docker Behind a Proxy - Web Code Geeks - 2026<\/title>\n<meta name=\"description\" content=\"In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Using Docker Behind a Proxy - Web Code Geeks - 2026\" \/>\n<meta property=\"og:description\" content=\"In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/\" \/>\n<meta property=\"og:site_name\" content=\"Web Code Geeks\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/webcodegeeks\" \/>\n<meta property=\"article:published_time\" content=\"2017-03-30T09:15:34+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"150\" \/>\n\t<meta property=\"og:image:height\" content=\"150\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Benjamin Cane\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@webcodegeeks\" \/>\n<meta name=\"twitter:site\" content=\"@webcodegeeks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Benjamin Cane\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/\"},\"author\":{\"name\":\"Benjamin Cane\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/4f5d918df9c19fab91b5b205357ce0b8\"},\"headline\":\"Using Docker Behind a Proxy\",\"datePublished\":\"2017-03-30T09:15:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/\"},\"wordCount\":1035,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg\",\"keywords\":[\"Docker\"],\"articleSection\":[\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/\",\"url\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/\",\"name\":\"Using Docker Behind a Proxy - Web Code Geeks - 2026\",\"isPartOf\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg\",\"datePublished\":\"2017-03-30T09:15:34+00:00\",\"description\":\"In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use\",\"breadcrumb\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage\",\"url\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg\",\"contentUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg\",\"width\":150,\"height\":150},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.webcodegeeks.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"DevOps\",\"item\":\"https:\/\/www.webcodegeeks.com\/category\/devops\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Using Docker Behind a Proxy\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#website\",\"url\":\"https:\/\/www.webcodegeeks.com\/\",\"name\":\"Web Code Geeks\",\"description\":\"Web Developers Resource Center\",\"publisher\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.webcodegeeks.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#organization\",\"name\":\"Exelixis Media P.C.\",\"url\":\"https:\/\/www.webcodegeeks.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png\",\"contentUrl\":\"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png\",\"width\":864,\"height\":246,\"caption\":\"Exelixis Media P.C.\"},\"image\":{\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/webcodegeeks\",\"https:\/\/x.com\/webcodegeeks\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/4f5d918df9c19fab91b5b205357ce0b8\",\"name\":\"Benjamin Cane\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/09c6af2f1a7430456089189937094b817ef1b7c75ab9968bfd3ec35d938d914b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/09c6af2f1a7430456089189937094b817ef1b7c75ab9968bfd3ec35d938d914b?s=96&d=mm&r=g\",\"caption\":\"Benjamin Cane\"},\"description\":\"Benjamin Cane is a systems architect in the financial services industry. He writes about Linux systems administration on his blog and has recently published his first book, Red Hat Enterprise Linux Troubleshooting Guide.\",\"url\":\"https:\/\/www.webcodegeeks.com\/author\/benjamin-cane\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Using Docker Behind a Proxy - Web Code Geeks - 2026","description":"In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/","og_locale":"en_US","og_type":"article","og_title":"Using Docker Behind a Proxy - Web Code Geeks - 2026","og_description":"In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use","og_url":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/","og_site_name":"Web Code Geeks","article_publisher":"https:\/\/www.facebook.com\/webcodegeeks","article_published_time":"2017-03-30T09:15:34+00:00","og_image":[{"width":150,"height":150,"url":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg","type":"image\/jpeg"}],"author":"Benjamin Cane","twitter_card":"summary_large_image","twitter_creator":"@webcodegeeks","twitter_site":"@webcodegeeks","twitter_misc":{"Written by":"Benjamin Cane","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#article","isPartOf":{"@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/"},"author":{"name":"Benjamin Cane","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/4f5d918df9c19fab91b5b205357ce0b8"},"headline":"Using Docker Behind a Proxy","datePublished":"2017-03-30T09:15:34+00:00","mainEntityOfPage":{"@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/"},"wordCount":1035,"commentCount":0,"publisher":{"@id":"https:\/\/www.webcodegeeks.com\/#organization"},"image":{"@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage"},"thumbnailUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg","keywords":["Docker"],"articleSection":["DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/","url":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/","name":"Using Docker Behind a Proxy - Web Code Geeks - 2026","isPartOf":{"@id":"https:\/\/www.webcodegeeks.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage"},"image":{"@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage"},"thumbnailUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg","datePublished":"2017-03-30T09:15:34+00:00","description":"In today\u2019s article, I am going to explore a common pain point for anyone running Docker in a large corporate environment. Today I\u2019ll show how to use","breadcrumb":{"@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#primaryimage","url":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg","contentUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2016\/01\/docker-logo.jpg","width":150,"height":150},{"@type":"BreadcrumbList","@id":"https:\/\/www.webcodegeeks.com\/devops\/using-docker-behind-proxy\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.webcodegeeks.com\/"},{"@type":"ListItem","position":2,"name":"DevOps","item":"https:\/\/www.webcodegeeks.com\/category\/devops\/"},{"@type":"ListItem","position":3,"name":"Using Docker Behind a Proxy"}]},{"@type":"WebSite","@id":"https:\/\/www.webcodegeeks.com\/#website","url":"https:\/\/www.webcodegeeks.com\/","name":"Web Code Geeks","description":"Web Developers Resource Center","publisher":{"@id":"https:\/\/www.webcodegeeks.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.webcodegeeks.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.webcodegeeks.com\/#organization","name":"Exelixis Media P.C.","url":"https:\/\/www.webcodegeeks.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png","contentUrl":"https:\/\/www.webcodegeeks.com\/wp-content\/uploads\/2022\/06\/exelixis-logo.png","width":864,"height":246,"caption":"Exelixis Media P.C."},"image":{"@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/webcodegeeks","https:\/\/x.com\/webcodegeeks"]},{"@type":"Person","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/4f5d918df9c19fab91b5b205357ce0b8","name":"Benjamin Cane","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.webcodegeeks.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/09c6af2f1a7430456089189937094b817ef1b7c75ab9968bfd3ec35d938d914b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/09c6af2f1a7430456089189937094b817ef1b7c75ab9968bfd3ec35d938d914b?s=96&d=mm&r=g","caption":"Benjamin Cane"},"description":"Benjamin Cane is a systems architect in the financial services industry. He writes about Linux systems administration on his blog and has recently published his first book, Red Hat Enterprise Linux Troubleshooting Guide.","url":"https:\/\/www.webcodegeeks.com\/author\/benjamin-cane\/"}]}},"_links":{"self":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/posts\/16745","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/users\/158"}],"replies":[{"embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/comments?post=16745"}],"version-history":[{"count":0,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/posts\/16745\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/media\/10356"}],"wp:attachment":[{"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/media?parent=16745"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/categories?post=16745"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.webcodegeeks.com\/wp-json\/wp\/v2\/tags?post=16745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}