Scott

That’s fine. We just treat it as a fork from this point onwards.

So disappointing.

Yep. I have two at the same time.

If you use an app like RethinkDNS, it will allow you to run multiple, simultaneous VPN connections and then choose how you want to route your traffic.

I have the same situation as you. I run two VPN connections. One to home and one to a VPS. I route all traffic to 10/8 to the home VPN, certain apps to my VPS VPN and then the rest of the traffic via the local connection.

RethinkDNS also does local DNS filtering and allows you to specify which DNS service to use. I run my own DoT service that backs off to the PiHole at home.

You need to add backslashes to your underscores since Markdown is turning them into italics.

¯\\\_(ツ)\_/¯

yields

¯\_(ツ)_/¯

You will need to be more specific on your configuration for us to provide a more comprehensive response.

I have Pihole configured with Mullvad as the primary upstream DNS provider (albeit with DoH).

Just make sure you’re using IP addresses for the upstream Mullvad DNS servers since you won’t be able to resolve their names without first having DNS (i.e. chicken-egg).

I feel that the craft itself would be shielded so that the extraneous stuff inside doesn’t have to be.

Notifications are instant for me, using a self-hosted Unified Push server too.

“Land of the free, home of the brave.”

Gimme a break.

OP used the word “siff” instead of the word “sift”.

*sift

Containers are just processes with flags. Those flags isolate the process’s filesystem, memory [1], etc.

The advantages of containers is that the software dependencies can be unique per container and not conflict with others. There are no significant disadvantages.

Without containers, if software A has the same dependency as software B but need different versions of that dependency, you’ll have issues.

[1] These all depend on how the containers are configured. These are not hard isolation but better than just running on the bare OS.