GoodiesHQ
Recommend disabling or exposing Caddy admin port in Dockerfile/Caddyfile
Had to docker build as i'm running on arm and then ran into an issue because i run under host networking that the default Caddyfile config that comes with headscale comes with the admin 2019 port active, might be worth it to disable that by default just for others that are running headscale/caddy in host network so it avoids the collission on 2019...
or maybe just expose the admin port as an ENV variable.
While this is possible, the headscale and headscale-admin containers are separate, so they can both listen on 2019 and the docker compose file can just redirect some other port to internal port 2019. I'm just not sure what benefit choosing the port 2019 provides when it can be redirected to from another port anyways. If you have a justification I'm happy to include it, doesn't seem like a big change at all.
