Public | Automated Build

Last pushed: 2 years ago
Short Description
Short description is empty for this repo.
Full Description

Transparent Squid in a container

This is a trivial Dockerfile to build a proxy container powered by famous Squid.

It is a shameless rip-off of jpetazzo/squid-in-a-can. Sorry for that :-)


When I started this fork, I was looking for a way to transparently mirror Docker registry so that I could get images
faster while just having to download once from the public registry. After many tries, it seems Squid is not exactly what one
needs to implement this idea. docker-registry supports mirroring and that's I'll be using from now on. Don't expect
any updates to this repository unless I come back at using Squid for other purposes.


If you build a lot of containers, and have a not-so-fast internet link,
you might be spending a lot of time waiting for packages to download.
It would be nice if all those downloads could be automatically cached,
without tweaking your Dockerfiles, right?

Or, maybe your corporate network forbids direct outside access, and require
you to use a proxy. Then you can edit this recipe so that it cascades to the
corporate proxy. Your containers will use the transparent proxy, which itself
will pass along to the corporate proxy.


You can use the squid proxy directly via docker. For more
information on tuning parameters see below.

Using Docker

You can manually run these commands

docker run --net host -d pires/docker-squid


That's it. Now all HTTP requests going through your Docker host will be routed through the proxy running in the container.

Note: it will only affect HTTP traffic configured to pass through this proxy.

Note: traffic originating from the host will not be affected.


The pires/squid-in-a-can container runs a really basic Squid3 proxy.
Rather than writing my own configuration file, I patch the default Debian

Then, this container should be started using the network namespace of the
(that's what the --net host option is for).
Another strategy would be to start the container with its own namespace.
Then, the HTTP traffic can be directed to it with a DNAT rule.
The problem with this approach, is that Squid will "see" the traffic as
being directed to its own IP address, instead of the destination HTTP
server IP address; and since Squid 3.3, it refuses to honor such requests.

(The reasoning is, that it would then have to trust the HTTP Host:
header to know where to send the request. You can check CVE-2009-0801
for details.)


The docker image can be tuned using environment variables.


Squid has a maximum object cache size. Often when caching debian packages vs
standard web content it is valuable to increase this size. Use the
-e MAX_CACHE_OBJECT=1024 to set the max object size (in MB)


The squid disk cache size can be tuned. use
-e DISK_CACHE_SIZE=5000 to set the disk cache size (in MB)

Persistent Cache

Being docker when the instance exits the cached content immediately goes away
when the instance stops. To avoid this you can use a mounted volume. The cache
location is /var/cache/squid3 so if you mount that as a volume you can get
persistent caching. Use -v /home/user/persistent_squid_cache:/var/squid3/cache
in your command line to enable persistent caching.


Ideas for improvement:

  • easy chaining to an upstream proxy
Docker Pull Command
Source Repository