6.2.0-stretch,6.2-stretch,6-stretch,stretch,6.2.0,6.2,6,latest(6.2/stretch/Dockerfile)6.2.0-alpine3.8,6.2-alpine3.8,6-alpine3.8,alpine3.8,6.2.0-alpine,6.2-alpine,6-alpine,alpine(6.2/alpine3.8/Dockerfile)6.0.3-stretch,6.0-stretch,6-lts-stretch,lts-stretch,6.0.3,6.0,6-lts,lts(6.0/stretch/Dockerfile)6.0.3-alpine3.8,6.0-alpine3.8,6-lts-alpine3.8,lts-alpine3.8,6.0.3-alpine,6.0-alpine,6-lts-alpine,lts-alpine(6.0/alpine3.8/Dockerfile)4.1.11-stretch,4.1-stretch,4-stretch,4-lts-stretch,4.1.11,4.1,4,4-lts(4.1/stretch/Dockerfile)4.1.11-alpine3.8,4.1-alpine3.8,4-alpine3.8,4-lts-alpine3.8,4.1.11-alpine,4.1-alpine,4-alpine,4-lts-alpine(4.1/alpine3.8/Dockerfile)
-
Where to file issues:
https://github.com/coopTilleuls/docker-varnish/issues -
Maintained by:
the Varnish Docker Community
- Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
Varnish is an HTTP accelerator designed for content-heavy dynamic web sites as well as APIs. In contrast to other web accelerators, such as Squid, which began life as a client-side cache, or Apache and nginx, which are primarily origin servers, Varnish was designed as an HTTP accelerator. Varnish is focused exclusively on HTTP, unlike other proxy servers that often support FTP, SMTP and other network protocols.
Create a default.vcl file:
vcl 4.0;
backend default {
.host = "www.nytimes.com";
.port = "80";
}Then run:
$ docker run --name my-running-varnish -v /path/to/default.vcl:/usr/local/etc/varnish/default.vcl:ro --tmpfs /usr/local/var/varnish:exec -d cooptilleuls/varnishAlternatively, a simple Dockerfile can be used to generate a new image that includes the necessary default.vcl (which is a much cleaner solution than the bind mount above):
FROM cooptilleuls/varnish:6.2
COPY default.vcl /usr/local/etc/varnish/Place this file in the same directory as your default.vcl, run docker build -t my-varnish ., then start your container:
$ docker run --name my-running-varnish --tmpfs /usr/local/var/varnish:exec -d my-varnish$ docker run --name my-running-varnish --tmpfs /usr/local/var/varnish:exec -d -p 8080:80 my-varnishThen you can hit http://localhost:8080 or http://host-ip:8080 in your browser.
VMODs are extensions written for Varnish Cache.
Install VMODs in your Varnish project's Dockerfile. For example, to install the vmod-querystring module:
FROM cooptilleuls/varnish:6.2
# install vmod-querystring
ENV VMOD_QUERYSTRING_VERSION 1.0.5
RUN set -eux; \
\
fetchDeps=' \
ca-certificates \
wget \
'; \
buildDeps=" \
$VMOD_BUILD_DEPS \
dpkg-dev \
"; \
apt-get update; \
apt-get install -y --no-install-recommends $fetchDeps $buildDeps; \
rm -rf /var/lib/apt/lists/*; \
\
wget -O vmod-querystring.tar.gz "https://github.com/Dridi/libvmod-querystring/releases/download/v$VMOD_QUERYSTRING_VERSION/vmod-querystring-$VMOD_QUERYSTRING_VERSION.tar.gz"; \
mkdir -p /usr/local/src/vmod-querystring; \
tar -zxf vmod-querystring.tar.gz -C /usr/local/src/vmod-querystring --strip-components=1; \
rm vmod-querystring.tar.gz; \
\
cd /usr/local/src/vmod-querystring; \
gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; \
./configure \
--build="$gnuArch" \
; \
make -j "$(nproc)"; \
make install; \
\
cd /; \
rm -rf /usr/local/src/vmod-querystring; \
\
apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false $fetchDeps $buildDepsThe cooptilleuls/varnish images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
Some of these tags may have names like stretch in them. These are the suite code names for releases of Debian and indicate which release the image is based on.
This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.