Lets see…

• nord vpn client
• qbittorrent (through nord vpn)
• proxy server (through nord vpn)
• wireguard vpn server
• ssh client so I can port forward through the vpn server to/from connected clients
• jellyfin
• ntfy (self hosted notifications)
• pi-hole (vital for the local dns)
• nginx
• gitea
• wallabag
• minecraft server
• container registery
• smb share for my friend (I help them with content creation)
• smb share for a live recording profile I set up on android

Those are just docker containers, it also is a backup server for all the devices I own. It also runs all non sensitive data on an unencrypted partition then will auto decrypt the sensitive partion through ssh via my desktop. This means my vpn server will always run so I can connect, wake on lan my desktop, decrypt it and log in. Im sure I’m missing things.

deleted by creator

I’m not sure if its applicable for you or if you are aware but duckdns really helps with this problem. I’ve moved three times since and have never worried about ip addresses.

Maybe mention that sooner next time instead of just disagreeing

My apologies, I see.

This whole post is in the context of virtual machines, and the claim you felt exactly opposite about was that docker will mess up VM networking. If you don’t use a network bridge with KVM that’s fair but I’m not sure why you would disagree with advice to a problematic situation only because it does not apply to you.

Docker will block networking to KVM VM’s if they are configured with a network bridge, aka giving the VM’s their own LAN IP address. I had so much trouble I switched to podman. Also, you’ve been working with containers for 5 years and call them dockers? Not the strongest ethos based claim.