Was this the correct course of action for updating the servers, /g/?
Proxmox is a disaster, he should have just used libvirt or raw qemu+systemd https://wiki.archlinux.org/title/QEMU#With_systemd_serviceNever trust this stupid web gui abstraction shit with anything that matters, he should just learn to use the tools directly.
>>108106130>internet dramaYou know that shit is the equivalent of soap opera, right? Is your life really this boring and irrelevant like you have the need to stalk mental ill people (aka lolcow) with Internet acces?
>>108106130Should've used NixOS
>>108106242i use it on my spare computer that i keep running headless for VMs and containers. what is an equivalent setup that lets me spin up, delete, and manager containers and VMs easily.
>>108106506ssh and libvirt's virsh handles both containers and vms https://www.libvirt.org/manpages/virsh.html
>>108106130Lol girl /g/ doesn't know what they're doing
lolcows are sad but people who go out of their way to talk about them aren't exactly so far ahead either
>>108106589so do you just choose some random distro like debian to be your hypervisor or can it be booted into standalone?
anyone who uses kiwifarms is a braindead dumb nigger and you posting it here should get you banned and raped
>>108106820The hypervisor is KVM, which is part of the linux kernel so Debian or Arch depending on your needs, Debian is what I would suggest to anyone who doesn't want the latest stuff to tinker with, you can always run Arch VMs and containers as needed. Docker/Podman can run on the host or in a VM normally without any extra steps if you need them.It's a much simpler setup with less moving parts to fail when you're just on a normal distro using libvirt or qemu command line directly and has saved me many personal headaches associates have went through with Proxmox over the years, some of which I gave this same advice to and have later thanked me for it.
>>108106868Just use cockpit
>>108106878I don't need it, and Josh shouldn't need it either because it's one more thing to break, the less middle man software you use the less you have to deal with these situations and the potential cost of the downtime.
>>108106130>server warns me that our SSH version can be compromised by modern attack vectors.Is he disclosing that the site had a major vulnerability for a while and nobody found it? Based retard if so. I thought trannies were supposed to be good at programming.
>>108106910>the site had a major vulnerability for a whileI realize now the irony of saying that on 4chan.
>>108106910>>108106916Yes but he said it after updating instead of it being exploited and forcing him to update like 4chan's exploit.
>>108106868realistically what is your process for spinning up a fresh vm or container? because i like that proxmox just lets me use a gui to destroy or create stuff. it kind of sounds like i will be remoting into some DE hosted by the arch/debian install and manually spinning stuff up
>>108106932well his statement states that the package announced that it was vulnerable for as long as it was there so he truly was just retarded or lazy
>>108107154You can interact with virsh entirely from the command line without needing to install a desktop on the server, virt-install is the tool you'll use for initial setup of a vm or lxc container https://man.archlinux.org/man/virt-install.1 the manual has a few examples. You can also give the manuals to an AI and ask it to make an example command to give you a starting point eg "create a virt-install command to set up a debian virtual machine with 4gb of ram and a 60gb drive", or you can use virt-manager which is a GTK gui that can run on your local system and connect to your server via ssh in the dialog under file->add connection to manage it.You can try all of this out in your existing environment with nested virtualization and learn how it all works and if it's worth implementing on bare metal https://pve.proxmox.com/wiki/Nested_VirtualizationOnce you've got familiar with libvirt commands it's very simple and straight forward to manage and keeps the rest of the system "stock" so you don't have to deal with anything like symlinked ssh keys.
>>108107337is there any real benefit to doing it this way. my needs are pretty bare. i host a nextcloud/caddy instance for file/photo redundancy and jellyfin/qbitorrent for pirating movies+shows for my family and kids. i've done so for the last 4 years and haven't had a problem yet. your suggestion sounds good if you are familiar enough with qemu to know what you're looking at from bare config files but if you're a washed up moron dadbod like myself things like promxox make it a lot easier to double click to win some container and iso and have something up and running with an easy GUI to manage from
>>108107442If it works for you locally and hasn't broken keep using it, it's not like you're running a big website that's under constant attack that should be minimizing attack surface and tech debt. If you're not trying to "color outside the lines" Proxmox does fine for a small local environment like that.
>>108106130I run this stuff with zero downtime and I update them every time update comes out as well.I run the exact same way he does pretty much with Debian.Proxmox update is as easy as apt full upgrade.Proxmox also has it so you can run two redundant servers, update one, while the other one takes over, and then when it is done updating, you switch to the updated one and update the other one.In essence, he sucks.
