I am running Caddy through docker (with sudo docker-compose up, yml is listed above). I know, sudo:ing docker isn’t best practice, but I’m learning the ropes in a non-production enviorment 🙃 Also, I verified that docker is running as root by ps -eo euser,ruser,suser,fuser,f,comm,label |grep caddy
As for the docker version, I verified it by inspecting the image ID and saw that the image version is 2.7.2:
<span style="color:#323232;"> "Labels": {
</span><span style="color:#323232;"> "org.opencontainers.image.description": "a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go",
</span><span style="color:#323232;"> "org.opencontainers.image.documentation": "https://caddyserver.com/docs",
</span><span style="color:#323232;"> "org.opencontainers.image.licenses": "Apache-2.0",
</span><span style="color:#323232;"> "org.opencontainers.image.source": "https://github.com/caddyserver/caddy-docker",
</span><span style="color:#323232;"> "org.opencontainers.image.title": "Caddy",
</span><span style="color:#323232;"> "org.opencontainers.image.url": "https://caddyserver.com",
</span><span style="color:#323232;"> "org.opencontainers.image.vendor": "Light Code Labs",
</span><span style="color:#323232;"> "org.opencontainers.image.version": "v2.7.2"
</span><span style="color:#323232;"> }
</span>
It seems that my next step is to look into the issue why dockerized-Caddy can’t communicate with Tailscale. Now I have a direction to investigate further into 🙂