I’ve had my dev VM upgraded to Debian 11 for a few months, and have fiddled with from time to time. It’s not that I distrust Debian stable in the slightest to not be stable, but I also am not going to just throw prod a sudo apt full-upgrade (yes, with updating sources first…) and hope for the best. As I didn’t experience any issues with workflow with the upgraded VM, I decided it was time to bake some new images....
I may have mentioned this before, but I have two nearly identical Supermicro 2Us. One is the main server that hosts VMs under Proxmox to do various tasks - a NAS, a Docker host, jumpbox, etc. The other came about because I discovered that its motherboard hardware revision level was too old to support Xeon v2 (Ivy Bridge), even with an updated BIOS. I wanted the lower thermals that v2s offered, so I bought a newer motherboard, and then got another 2U case to throw the old motherboard and CPU into....
In case you haven’t been following my work (I absolutely can’t blame you, as this blog is self-congratulatory at best), I have a 25U rack with some stuff in it. In short, it consists of a Supermicro 2U X9, and a ZFS pool, with an almost-identical second Supermicro 2U X9 that exists as a cold spare, and a ZFS backup target. There’s also a Dell R620 1U that I’ve done absolutely nothing with yet beyond installing Proxmox....
I’ve now accomplished one of my previously-mentioned desires, namely, to use Packer to make VMs for Proxmox. After much battling with YAML and esoteric bash commands, I have succeeded in being able to spawn endless VMs, ready to go just how I like them. As with many projects I’ve done, this was thanks to someone else’s hard work; I merely customized it. The repo[s] are in two parts, and for my forks, only the Debian template has been customized....
A friend wanted to learn Linux, so I offered to spin up a VM under Proxmox. Done. Just kidding. I mean, that would work (assuming you handled port forwarding) if you were hitting an IP, but FQDNs are much easier for people to remember. Except ssh isn’t based on HTTP, so how do you forward them? One way is with nginx’s stream module. Something like this suffices. stream { upstream ssh { server $DEST_IP:$SSH_PORT; } server { listen $FORWARDED_PORT; proxy_pass ssh; } } And that’ll handle one person just fine....