I asked myself the same question before. If only caddy had an official image with the cloudflare plugin, so we wouldn’t have to build ourselves or trust 3rd party providers. But oh well, if you have any other custom image, you might as well build caddy as well.
I’m not entirely sure, but I think you can skip the “–no-cache” as it seems to still check for image updates. It helps to speed things up, especially if you check for updates more frequently.
Note that the (non-windows) caddy and caddy: builder images are all alpine based. The “-alpine” tags point to the same images (as you can tell by the hashes). But some like to be explicit about it 💜.
At work I use kubernetes and quite like that (upgrading containers without downtime FTE), but I didn’t bother trying to set up the infrastructure myself. Some argue, it’s not with the efford for self hosting, I dunno.
What I do like to use is Dockge, to keep docker but also keep your sanity. It even offers a single button for “docker compose pull”, which is great of you don’t have to many compose files / stacks. Combine with a simple shell script to batch pull/build all stacks in one go, plus some backup solution, and it’s actually nice to use and does all that I need. I love CLIs, but I’ve had situations where the GUI came in very handy.
#! /bin/bash
# note: this will update and START all dockge stacks, even if you stopped them before
shopt -s nullglob
for proj in /opt/dockge /opt/stacks/*/; do
echo "> $proj"
docker compose -f "$proj/compose.yaml" up --pull always --build --detach
echo ""
done
[Test] around and find out