roadmap VS lima

x86-64 containers?

https://github.com/docker/roadmap/issues/384 is still open. :(

Request features or give feedback: https://github.com/docker/roadmap/issues/524

Nothing in the road map [Github] returned by searching 'stop'.

Further reading online revealed that host network mode is not available for swarm started with docker stack deploy. (Possible related open issue: github link).

Single-click k8s install. Extensions. Init. And there are people who just prefer an app-based experience for their own reasons - I think it was the most "upvoted" request ever on their public roadmap.

In case you need to run x86 containers: Docker has Rosetta support now but it's buggy.

https://github.com/docker/roadmap/issues/384

Without Rosetta it uses relatively slow Qemu emulation.

https://github.com/docker/roadmap/issues/44

So, at the moment, any public organization images are doomed to be lost, if they won't pay.

I've been watching this GitHub issue for damn near 3 years. Filesystem performance is pretty bad, depending on what you're doing. I had to kludge together workarounds to my DX at my last role where we used Docker for development. It was really, really painful and distracting.

[2] https://github.com/docker/roadmap/issues/7

You can run a virtual machine (e.g. lima) from inside a nix-shell, exactly as you would do with a regular shell.

for others similarly curious, here's an example of the thing: https://github.com/noop-inc/template-java-spring-boot/blob/m...

they seem to be using the excellent lima <https://github.com/lima-vm/lima#readme> for booting on macOS; I run colima for its containerd and k8s support but strongly recommend both projects $(brew install lima colima)

Lima is what I use as well. It's quick and easy to just fire up a VM with default settings, but also very easy to configure with different file sharing options, port forwarding, different linux distributions, etc. (their examples are also pretty good IMO [1]).

In particular I use it to run an amd64 VM, which I need to run a stubborn service for work that doesn't run on arm CPUs.

[1] https://github.com/lima-vm/lima/tree/master/examples

Lima (1) is a project that packages Linux distros for MacOS and executes them via qemu in the backend. Maybe you could solve your problem by launching one of their vms and inspecting the command line it generates. You might find an option you were missing.

(1) https://github.com/lima-vm/lima

If you wish to delve into all the configuration possibilities for Lima VM, you can visit this resource.

I'd say Lima and Colima should be enough for most use cases:

https://lima-vm.io/

https://github.com/abiosoft/colima

Github: https://github.com/lima-vm/lima

Lima wraps QEMU in a simple CLI, with neat features for container users, such as filesystem sharing and automatic localhost port forwarding, as well as DNS and proxy propagation for enterprise networks. Rancher Desktop wraps Lima with k3s integration and GUI.

Talks: https://github.com/lima-vm/lima/blob/master/docs/talks.md