[dotnet00]

My personal biggest peeve is how Docker still doesn't play well with a VPN running on the host. It's incredibly annoying and an issue I frequently run into on my home setup.

It's crazy to me that people push it so much given this issue, aren't VPNs even more common in corporate settings, especially with remote work nowadays?

I find it easier to just spin up a full VM than deal with docker's sensitivities, and it feels a bit ridiculous to run a VM and then setup docker within it instead of just having appropriate VM images.

[byteknight]

I think that has more to do with not understanding routing and firewalls. Vpns usually have something called a kill switch that force tunnels all traffic to avoid leaks.

While I can see it does at times make it more difficult to do certain things with the proper permissions, know how and set up there is nothing it cannot do.

[dotnet00]

So we're back to where we started, just tinker "a little" with the setup to try to make it work, exactly the issue Docker claimed to be aimed at solving.

I tried running a docker based setup for a year on my homeserver, thinking that using it for some time would help me get over my instinctive revulsion towards software that makes Docker the only way to use it, the way that forcing myself to use Python had helped me get over disdain for it back during the early days of the transition from 2 to 3. Didn't help at all, it was still a pita to rely on. Went back to proper installs, couldn't be happier.

[byteknight]

How is that any different than any software? Configuration and trial and error is the name of the game no matter your stack...