What are people using Vagrant for these days? The last time I encountered it was before Docker become widespread.
ianeff
Mama, what a read! Nice work! Same story on macos: recently ditched the big (corpulent, distended, ossified) vagrant + virtualbox _repositories_ for some spritely lima + apple virtualization framework scripts, and been happier for it.
It was a forklift, to be sure, but the machines're snappier, & you buy yourself a little headroom.
veeti
I never got into Vagrant but "lima" has worked well for spinning up (temporary) VM's quick: https://lima-vm.io/
There's plenty of images for different distributions, automatic file sharing between host and guest, etc.
fulafel
For many use cases you'll do fine without the libvirt tower of babel, with just the qemu/kvm cli.
stefanha
virt-builder is an alternative to installing a guest OS from scratch. It has a selection of popular guest OSes template images that you can quickly install non-interactively.
It's convenient when you don't want to manually install a guest and also don't want to figure out preseed/kickstart/etc.
It makes creating new KVM guests easier and has handy features like the ability to copy in ssh keys so you can connect to the guest right away.
happyPersonR
There used to be virt-manager
Wonder if it’s still around ? Hope it’s doing well !
show comments
cortesoft
Most of my vagrant usage is from when a coworker has set up a vagrant file for a project.
SkipperCat
This is the first time in my entire life I've ever seen someone use a Plan 9 formatted disk. Deep respect.
show comments
zamadatix
This is another area I hope I'm able to migrate to systemd. I already use nspawn for containers but vmspawn is still a bit new and limited in the options. Once it gets there though it'll be nice to have system+containers+vms under one consistent roof.
exabrial
Honestly though... why not just systemd containers with minimal mounts, and if you're needing an ip, what not an unprivledged LXC container? The surface area is far smaller and they're way easier to inspect.
shellwizard
Have you tried distrobox/toolbox instead of having to spin up VMs? Also microvm looks nice
guilhas
vagrant, docker, qemu, lxc, libvirt, incus, proxmox, nixos, guix, incusos, talos, microVMs, distrobox, packer, distrobuilder, ansible, terraform, cloud-init... Just crazy layers of choice and combinations
Membership in the libvirt group is root-equivalent, not a permissions fix. Through qemu:///system it lets you attach arbitrary host block devices to a VM, so anyone in that group can mount and read the host's own disk. If you want to manage VMs without root or that group, use qemu:///session instead: unprivileged, images live under ~/.local/share/libvirt, no sudo. Tradeoff is you lose bridged networking without a setuid helper.
What are people using Vagrant for these days? The last time I encountered it was before Docker become widespread.
Mama, what a read! Nice work! Same story on macos: recently ditched the big (corpulent, distended, ossified) vagrant + virtualbox _repositories_ for some spritely lima + apple virtualization framework scripts, and been happier for it.
It was a forklift, to be sure, but the machines're snappier, & you buy yourself a little headroom.
I never got into Vagrant but "lima" has worked well for spinning up (temporary) VM's quick: https://lima-vm.io/
There's plenty of images for different distributions, automatic file sharing between host and guest, etc.
For many use cases you'll do fine without the libvirt tower of babel, with just the qemu/kvm cli.
virt-builder is an alternative to installing a guest OS from scratch. It has a selection of popular guest OSes template images that you can quickly install non-interactively.
It's convenient when you don't want to manually install a guest and also don't want to figure out preseed/kickstart/etc.
It makes creating new KVM guests easier and has handy features like the ability to copy in ssh keys so you can connect to the guest right away.
There used to be virt-manager
Wonder if it’s still around ? Hope it’s doing well !
Most of my vagrant usage is from when a coworker has set up a vagrant file for a project.
This is the first time in my entire life I've ever seen someone use a Plan 9 formatted disk. Deep respect.
This is another area I hope I'm able to migrate to systemd. I already use nspawn for containers but vmspawn is still a bit new and limited in the options. Once it gets there though it'll be nice to have system+containers+vms under one consistent roof.
Honestly though... why not just systemd containers with minimal mounts, and if you're needing an ip, what not an unprivledged LXC container? The surface area is far smaller and they're way easier to inspect.
Have you tried distrobox/toolbox instead of having to spin up VMs? Also microvm looks nice
vagrant, docker, qemu, lxc, libvirt, incus, proxmox, nixos, guix, incusos, talos, microVMs, distrobox, packer, distrobuilder, ansible, terraform, cloud-init... Just crazy layers of choice and combinations
I am trying vanilla qemu with cloud-init. Images: https://images.linuxcontainers.org/images/
Membership in the libvirt group is root-equivalent, not a permissions fix. Through qemu:///system it lets you attach arbitrary host block devices to a VM, so anyone in that group can mount and read the host's own disk. If you want to manage VMs without root or that group, use qemu:///session instead: unprivileged, images live under ~/.local/share/libvirt, no sudo. Tradeoff is you lose bridged networking without a setuid helper.