# Supported tags and respective `Dockerfile` links - [`6.3`, `6.3.0-1`, `6.3.0`, `6`, `latest`, `fresh`](https://github.com/varnish/docker-varnish/blob/50071fbb9b49fb793fd3570a647a6aa04fae6d7b/fresh/debian/Dockerfile) - [`6.0`, `6.0.4-1`, `6.0.4`, `stable`](https://github.com/varnish/docker-varnish/blob/62fa33d7e54b02665c4c898dd1d5234ab57e098d/stable/debian/Dockerfile) # Quick reference - **Where to get help**: [the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://blog.docker.com/2016/11/introducing-docker-community-directory-docker-community-slack/), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker) - **Where to file issues**: [https://github.com/varnish/docker-varnish/issues](https://github.com/varnish/docker-varnish/issues) - **Maintained by**: [the Varnish Docker Community](https://github.com/varnish/docker-varnish) - **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64)) [`amd64`](https://hub.docker.com/r/amd64/varnish/) - **Published image artifact details**: [repo-info repo's `repos/varnish/` directory](https://github.com/docker-library/repo-info/blob/master/repos/varnish) ([history](https://github.com/docker-library/repo-info/commits/master/repos/varnish)) (image metadata, transfer size, etc) - **Image updates**: [official-images PRs with label `library/varnish`](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Fvarnish) [official-images repo's `library/varnish` file](https://github.com/docker-library/official-images/blob/master/library/varnish) ([history](https://github.com/docker-library/official-images/commits/master/library/varnish)) - **Source of this description**: [docs repo's `varnish/` directory](https://github.com/docker-library/docs/tree/master/varnish) ([history](https://github.com/docker-library/docs/commits/master/varnish)) # What is Varnish? 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. > [wikipedia.org/wiki/Varnish_(software)](https://en.wikipedia.org/wiki/Varnish_(software))  # How to use this image. ## Basic usage Create a `default.vcl` file: ```vcl vcl 4.0; backend default { .host = "www.nytimes.com:80"; } ``` Then run: ```console $ docker run --name my-running-varnish -v /path/to/default.vcl:/etc/varnish/default.vcl:ro --tmpfs /usr/local/var/varnish:exec -d varnish ``` Alternatively, 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): ```dockerfile FROM varnish:6.2 COPY default.vcl /etc/varnish/ ``` Place this file in the same directory as your `default.vcl`, run `docker build -t my-varnish .`, then start your container: ```console $ docker run --name my-running-varnish --tmpfs /var/lib/varnish:exec -d my-varnish ``` ### Exposing the port ```console $ docker run --name my-running-varnish --tmpfs /usr/local/var/varnish:exec -d -p 8080:80 my-varnish ``` Then you can hit `http://localhost:8080` or `http://host-ip:8080` in your browser. # License View [license information](https://github.com/varnishcache/varnish-cache/blob/master/LICENSE) 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). Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `varnish/` directory](https://github.com/docker-library/repo-info/tree/master/repos/varnish). 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.