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 are partitioned off into separate vms in proxmox and vscode’s remote ssh plus easy port forwarding helps a lot in making the whole thing feel local.

However I just recently experienced an internet interruption and thus felt a downside of this workflow: my vms and docker containers are not connectable anymore 🙁

I can still connect my local computer via hotspot, bit proxmox really likes it’s wired connection and doesn’t make wireless connections easy.

I might have to look into some sort of mobile 5g to Ethernet (or wifi extender to Ethernet) that I can use for these cases. So when the internet goes down and I happen to have mobile 5g, I can just connect the home network to use that as the upstream and have everything still connected to the internet (albeit slowly).

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply