containarr VS gluetun

not with containarr

Hijacking: I have an example of a good practice here. Feel free to look through the repository's structure, and the configurations in use for inspiration.

quick update: Making alternate configs is a bit more involved than I thought because I hadn't thought about it much. This is being addressed in milestone v0.3.0

"Hi, this is ray the developer of containarr. /u/bigbeansinyachin is an alt account that I made before this one because, well, I hadn't really intended to make a permanent reddit account again before now. But, in the interest of accepting reddit's value in spuring discussion I've decided to change my stance. You can check further development by following at https://github.com/ray-rock/containarr or by going to my account and following up there. I will be back when its time to drop the newest release. In the meantime, I'd like to thank everyone who has participated in this discussion, and those who have followed up on github. Your feedback helps drive this project and introduces me to new concepts, tools, and approaches I might not have otherwise considered. I'll check back periodically to gather/reply to any new feedback before the next release."

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki