This message was deleted.

It would be easier to use Kind or K3d on Windows

Can you elaborate on why this is?

It’s made for the task

Please elaborate on what features makes k3d more applicable to my use case. I would like to understand this better.

Hey Mark, I think that Ibingchong is pointing at, is that “wiring” the port mapping between WSL and the host could be tricky and not documented yet. While in the other hand k3d is designed around running k3s as container (within a vm with docker) having it mind its limitations. So using the k3d cli to do the port mapping between the docker vm + containers to your host feels easier.

Thanks for the response, much appreciated. When I run docker on WSL I'm running directly on the WSL distro (I don't user docker desktop). So I'm basically running in a container running on Microsoft Mariner running under hyper-v. I was surprised by your statement that “wiring” the port mapping between WSL and the host is not documented yet. Is there a bug/effort to clarify this. I would be happy to get involved in any current efforts,

I'm not a maintainer, but I think that issue is not in K3s or K3d roadmap

we’re not really working on this. For running in hyper-v, rancher desktop already has most of that logic handled. For running natively on windows, MS has a PR open to contribute native k3s agent support. The middle ground, we don’t really have any interest in exploring.

Many thanks for the info, much appreciated, I will give this some more thought