Downside of a virtualized workflow

I’ve been using a virtualized workflow for almost a year now, and it’s been great. My work for clients, projects, and specific interests is partitioned off into separate VMs in Proxmox, and VS Code’s Remote SSH plus easy port forwarding helps a lot in making the whole thing feel local.

However, I recently experienced an internet interruption and felt a downside of this workflow: my VMs and Docker containers were no longer reachable. 🙁

I can still connect my local computer via a hotspot, but Proxmox really likes its wired connection and doesn’t make wireless connections easy.

I might have to look into some sort of mobile 5G-to-Ethernet adapter (or Wi-Fi-extender-to-Ethernet setup) that I can use in these cases. Then, when the internet goes down and I happen to have mobile 5G, I can connect the home network to it as the upstream connection and have everything stay connected to the internet (albeit slowly).