procsiab/caddy repository overview

⁠Caddy Container

⁠How it works

This repository will help you create and deploy a container with the caddy proxy, with the CloudFlare DNS plugin compiled. Also, the container images for ARMv7, AARCH64 and x86_64 platforms are automatically built from this repository, and available from Docker Hub⁠

REMEMBER to pass the CADDYFILE_PATH environment variable to the container, defining it with the absolute path for the Caddyfile.

⁠Hashicorp Nomad Template

Following this⁠ the idea of the GitHub user optiz0r, which I read from this⁠ issue, I added a Bash signal handler, and changed the container entrypoint accordingly to run the handler and Caddy through Tini.

This way, I am able to send the SIGHUP through the Nomad Template stanza and have the Caddy process reload its configuration afterwards.

NOTE: In Caddy v1 SIGUSR1 was used to trigger the configuration reload, however it is still not supported in Nomad to pass that signal to allocations.

⁠Changing the configuration

To change the contents of Caddyfile and secrets.env without having Git to store your secrets, run the following git commands:

git update-index --assume-unchanged Caddyfile
git update-index --assume-unchanged secrets.env

⁠Build the image (optional)

The Containerfile is written to allow cross-architecture builds, using QEMU's user-static package: to build the image on x86 for another platform do the following:

• be sure to install qemu-user-static if you need to run the container on an architecture different from the local one;
• to build the container for aarch64, run cp $(which qemu-aarch64-static) .;
• run the build process with podman build -f Containerfile.aarch64 -t mycompany/caddy:latest-aarch64 ..

To build using a different Caddy version (e.g. 2.0.0), append the following argument on the command line to podman build:

--build-arg=caddyversion=2.0.0

NOTE: If you have built the image and want to use it with compose, you will need to change the image: statement into the podman-compose.yml file