4 ms·

I'm surprised the post title says "with focus on running containers". That would be Colima, AFAIK, which uses Lima but is a separate project. See https://github

by ilyagr 2y ago

I'm surprised the post title says "with focus on running containers". That would be Colima, AFAIK, which uses Lima but is a separate project. See https://github.com/abiosoft/colima https://github.com/abiosoft/colima. Colima is meant as a free replacement for Docker Desktop on Mac OS. Lima, OTOH, is more of a nice way to run a Linux VM on Mac in a way that integrates the guest and the host systems to a good degree by default. It wraps either QEMU or Apple's VZ framework. In my mind, Lima is spiritually similar to https://github.com/89luca89/distrobox https://github.com/89luca89/distrobox, but for a Mac host For a more traditional VM GUI, there's https://mac.getutm.app/ https://mac.getutm.app/ which is a completely separate free project that also wraps QEMU or VZ. It will run any OS you want, not just Linux.

yencabulator 2y ago
It seems Lima also wants to run containers, but using containerd: > The key difference is that Colima launches Docker by default, while Lima launches containerd by default. https://lima-vm.io/docs/faq/colima/ https://lima-vm.io/docs/faq/colima/
- mrbluecoat 2y ago
  Yes, it took me a minute to realize that but excited they support Apptainer
MuffinFlavored 2y ago
Being mean here: Why use either? Aren't they both just "opinionated" wrappers around this basically: qemu-system-aarch64 \ -M virt,accel=hvf \ -cpu host \ -smp cpus=8 \ -m 8192 \ -boot d \ -drive if=pflash,format=raw,file=/opt/homebrew/Cellar/qemu/9.0.0/share/qemu/edk2-aarch64-code.fd \ -drive if=virtio,format=qcow2,file=debian-12-nocloud-arm64.qcow2 \ -net nic \ -net user,hostfwd=tcp::2222-:22,hostfwd=tcp::6443-:6443 \ -device virtio-gpu-pci \ -device nec-usb-xhci \ -device usb-kbd \ -device usb-tablet \ -nographic
- mdaniel 2y ago
  followed by "the rest of the owl," since I doubt very seriously that debian-12-nocloud-arm64 boots up docker or containerd and your cited command does not mount $HOME in qemu such that $(docker run -v $HOME/work:/work debian:12) would do something reasonable from within the VM If you were interested, Brew also offers "opt" links to avoid hard-coding version numbers into paths: -drive if=pflash,format=raw,file=/opt/homebrew/opt/qemu/share/qemu/edk2-aarch64-code.fd \ and if one happens to be already running with $(brew shellenv) then -drive if=pflash,format=raw,file=${HOMEBREW_PREFIX}/opt/qemu/share/qemu/edk2-aarch64-code.fd \ will allow the script to work on both arm and x86_64 setups

by ilyagr 2y ago

yencabulator 2y ago

It seems Lima also wants to run containers, but using containerd: > The key difference is that Colima launches Docker by default, while Lima launches containerd by default. https://lima-vm.io/docs/faq/colima/ https://lima-vm.io/docs/faq/colima/

mrbluecoat 2y ago
Yes, it took me a minute to realize that but excited they support Apptainer

MuffinFlavored 2y ago

Being mean here: Why use either? Aren't they both just "opinionated" wrappers around this basically: qemu-system-aarch64 \ -M virt,accel=hvf \ -cpu host \ -smp cpus=8 \ -m 8192 \ -boot d \ -drive if=pflash,format=raw,file=/opt/homebrew/Cellar/qemu/9.0.0/share/qemu/edk2-aarch64-code.fd \ -drive if=virtio,format=qcow2,file=debian-12-nocloud-arm64.qcow2 \ -net nic \ -net user,hostfwd=tcp::2222-:22,hostfwd=tcp::6443-:6443 \ -device virtio-gpu-pci \ -device nec-usb-xhci \ -device usb-kbd \ -device usb-tablet \ -nographic

mdaniel 2y ago
followed by "the rest of the owl," since I doubt very seriously that debian-12-nocloud-arm64 boots up docker or containerd and your cited command does not mount $HOME in qemu such that $(docker run -v $HOME/work:/work debian:12) would do something reasonable from within the VM If you were interested, Brew also offers "opt" links to avoid hard-coding version numbers into paths: -drive if=pflash,format=raw,file=/opt/homebrew/opt/qemu/share/qemu/edk2-aarch64-code.fd \ and if one happens to be already running with $(brew shellenv) then -drive if=pflash,format=raw,file=${HOMEBREW_PREFIX}/opt/qemu/share/qemu/edk2-aarch64-code.fd \ will allow the script to work on both arm and x86_64 setups