jtyr/caddy repository overview

⁠docker-caddy

This is a Dockerfile which helps to create Docker container with minimalist HTTP server. The HTTP server is called Caddy⁠ and it's written in Go. This container is using statically compiled Caddy which means that there is only the caddy binarry plus few files in the container which makes the container very small:

$ docker images
REPOSITORY             TAG                 IMAGE ID            CREATED             SIZE
jtyr/caddy             latest              ae6b0f668182        5 seconds ago       11.3MB

⁠Usage

Build the image:

$ docker build -t jtyr/caddy .

Build with additional plugins (e.g. docker and tls.dns.exoscale):

$ docker build -t jtyr/caddy --build-arg plugins='github.com/lucaslorentz/caddy-docker-proxy/plugin github.com/caddyserver/dnsproviders/exoscale' .

Or pull the image directly from Docker Hub:

$ docker pull jtyr/caddy

Run the container:

$ docker run -p 2015:2015 jtyr/caddy

Now it should be possible to access the HTTP server on the host's local address:

$ curl http://localhost:2015

The default port 2015 can be changed by the Docker port mapping:

$ docker run -d -p 8080:2015 jtyr/caddy
$ curl http://localhost:8080

Content is serverd from the /data directory. In order to use the custom content, we have to mount a volume with the content:

$ docker run -d -p 2015:2015 -v /path/to/my/web/page:/data jtyr/caddy

Similarly the .caddy directory, containing for example the HTTPS certificates, can be shared across multiple containers like this:

$ docker run -d -p 2015:2015 -v /caddy/page:/data -v /caddy/.caddy:/.caddy jtyr/caddy

Configuration can be changed by mapping the default Candyfile to local one:

$ docker run -d -p 2015:2015 -v /caddy/Caddyfile:/Caddyfile jtyr/caddy

Additional settings (e.g. staging Let's Encrypt URL) can be appliad as an argument of the container:

$ docker run -d -p 2015:2015 -v /caddy/Caddyfile:/Caddyfile jtyr/caddy -ca https://acme-staging.api.letsencrypt.org/directory

If the automatic HTTPS is activated, both ports the 80 and the 443 can be mapped like this:

$ docker run -d -p 80:80 -p 443:443 -v /caddy/Caddyfile:/Caddyfile -v /caddy/.caddy:/.caddy jtyr/caddy

⁠License

MIT

⁠Author

Jiri Tyr