Windows-Containers VS lima

You're trading one convenience for a world of hurt if you use Kubernetes with Windows. Just take a casual glance at the "Windows containers" issues list on GitHub: https://github.com/microsoft/Windows-Containers/issues

Some of the very recently closed issues were jaw-dropping, such as totally broken networking in common scenarios.

DNS resolution is very different in Windows compared to Linux, making much of the "neatness" of Kubernetes pod-to-pod communication not work.

There is no maximum memory limit in Windows kernel "job objects" (equivalent to cgroups), so one memory leak in one pod can kill an entire node or cluster. This is very hard to solve, and I've seen it take out Service Fabric clusters also.

Etc, etc...

There is also a GitHub unresolved closed issue with similar issue: https://github.com/microsoft/Windows-Containers/issues/173

We keep checking for version compatibility with testing internally before releasing it externally. However, if something still breaks, you can expect a communication from Microsoft - most likely here: https://github.com/microsoft/Windows-Containers/issues

If you think this is a bug and want the Microsoft team to investigate, please file a an issue here: https://github.com/microsoft/Windows-Containers/issues (Please remember to post the resolution here so other Reddit users can also see that)

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