docker-cloudflared VS caddy-docker-proxy

Edit: Also great to see that AGH has secure DNS built in. My Pi-Hole solution required cloudflared [0] for that.

[0]https://github.com/crazy-max/docker-cloudflared

You can forward all unresolved DNS requests to Cloudflare on Pi-hole, but if you want to send them through DNS over HTTPS (DoH) on your network, you will need to forward them to something running cloudflared. Here are 2 docker containers you can use to host on separate network containers: https://github.com/crazy-max/docker-cloudflared, https://github.com/visibilityspots/dockerfile-cloudflared

There are multiple types of encrypted DNS services (DoH, DoT, DoQ). I have used DoH using cloudflared. If you are using Docker, you can use this.

My ISP was doing the same thing. It was only fixed after switching to DoH. OP, if you are using docker, you can use this one file solution to setup pihole+cloudflared. Repo source

Cloudflared - DNS over HTTPS client that's not tied to Cloudflare (route Pihole requests through this)

Caddy via Caddy Docker Proxy (network).

https://github.com/lucaslorentz/caddy-docker-proxy

It handles the routing to multiple dockerized projects on one server, by scanning docker compose files for labels and automatically setting up the required caddy configuration.

My go to is always this instead:

https://github.com/lucaslorentz/caddy-docker-proxy

Single label to a docker container and with correct DNS you’ll have an automatically managed certificate right away.

I have had a great experience with using this: https://github.com/lucaslorentz/caddy-docker-proxy

It combines caddy with docker-compose labels, making it super easy to spin up new projects that can immediately be exposed.

If you want a slightly heavier but more robust solution, caddy-docker-proxy[0] is a plugin that listens to the Docker socket and automatically updates the Caddy configuration based on Docker labels you add to containers.

I.e. it makes Caddy act a bit more like Traefik. Most of the time, you'll just add the label `caddy.reverse_proxy={{upstreams http 8080}}` to your containers and the plugin will regenerate Caddy's configuration whenever the container is modified.

[0] https://github.com/lucaslorentz/caddy-docker-proxy

I disagree, Caddy works great in Docker. See https://caddyserver.com/docs/running#docker-compose, and CDP is a project that autoconfigures Caddy from labels https://github.com/lucaslorentz/caddy-docker-proxy. Regarding plugins, it's super simple to write a Dockerfile to add plugins, we ship a builder image variant that can be used to compile in any plugins you want.

````

This way, Caddy will buffer the request and give 30 seconds for your new service to get online when you're deploying a new version.

Ideally, during deployment of a new version the new version should go live and healthy before caddy starts using it (and kills the old container). I've looked at https://github.com/Wowu/docker-rollout and https://github.com/lucaslorentz/caddy-docker-proxy but haven't had time to prioritize it yet.

Docker labels support is available via a plugin https://github.com/lucaslorentz/caddy-docker-proxy

Or caddy-docker-proxy: https://github.com/lucaslorentz/caddy-docker-proxy