go-mtree VS gluetun

go-mtree can take care about it. It calculates files hashes and you can use it to compare it later.

There is old unix utility called 'mtree' (there also is fully binary static compatible with mtree version on github go-mtree ) to check integrity of files. Another solution is - ZFS that do it dynamically

There is FreeBSD utility called mtree that also ported to Linux systems, that walk specified filesystem and creates hashes for all found content which later can be used to check integrity against corruption/modification. If your distribution of choice doesn't have ported version of mtree, you can use multiplatform version go-mtree that replicate the same workflow

go-mtree # Integrity

go-mtree: portable implementation of well known utility mtree) that can be used to save/test file's integrity as well directory structures. Open source, portable across most popular operation systems, no dependencies, single executable file.

There is standard utility for integrity testing mtree) that ported to linux too. Also there is multi platform version of upstream written in Go (read works everywhere from one single file) that called go-mtree

SHA1 is dead, and there is a better dedicated tool mtree(8) for such tasks (which by the way exists as implementation in Go as go-mtree ) but I believe OP wants to check versions (like fzf --version) not an integrity of files

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