caddy-docker-proxy generates a Caddyfile in memory, and then it calls the internal Caddy API `/load`. So - yes, it would presumably have been affected, at least from what I saw yesterday (with our own Caddy) and if the github issue I mentioned is correct.