core: Trouble running in Docker containers (or binding to 0.0.0.0) about caddy

[joeshaw]

You might want to go the nginx route of having a default_server that acts as a catch-all fallback when the Host header doesn't match any of the specified virtual hosts.

[joeshaw]

That'd let you separate the concerns of what IP address/interface the server binds to (ie, 0.0.0.0) versus the virtual hosts that it serves.

[abiosoft]

I have experienced this on my local pc without docker.

[darron]

Thanks for fixing this!

I created a Docker image for Caddy - https://github.com/darron/caddy-docker - but in order to do that and make a really small image I needed to statically link the final binary. The final Docker image was 23MB - vs using Ubuntu as a base image which was 148MB.

If possible, using your binaries would be better - people trust the author more than some random person compiling it - but you'd need to build them a little differently and statically link them.

Would that be possible for you to look at doing?

Thanks!

[mholt]

I could definitely look into it - I imagine that means more than just setting CGO_ENABLED=0 when building?

[darron]

A little - this is how I built it.

go get github.com/mholt/caddy
cd $GOROOT/src/github.com/mholt/caddy
CGO_ENABLED=0 go build -a -installsuffix cgo