innernet VS caddy-docker-proxy

Innernet is a barebone alternative. https://github.com/tonarino/innernet

Very relatable! At first, I struggled for days trying to make Netmaker or Innernet functional for my personal home server (Raspberry Pi behind multiple routers). But then I stumbled upon ZeroTier, and everything worked seamlessly within a couple of hours. Tailscale was actually the next one on my list because I heard many positive things about it over at r/selfhosted (especially about headscale). However, I did not end up testing it after ZeroTier worked.

Not if you are running wireguard without any management client/server like Netmaker or innernet or any of the many others like them.

I use the GCP free instance as my innernet coordination server (Wireguard mesh vpn). Which is extremely low traffic.

Or why not the open source tool innernet? https://github.com/tonarino/innernet

I wonder if this might improve over a more modern transport, if you were using an IPSec VPN.

Wireguard is enabling us to re-think what's possible over a VPN. Here's an example of what I mean. The network stack is based on Wireguard, with https://github.com/tonarino/innernet providing the topology and identity provisioning.

Virtual Private Network: Innernet, MASQ

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

I am trying now for some Days to use a Caddyfile additionaly to the auto generated files from lucas lorentzes caddy repositroy. https://github.com/lucaslorentz/caddy-docker-proxy