[btreecat]

This is something I find exciting! I was looking at our infrastructure and between all the various services, we basically have recreated k8s only more expensive and fragmented and tied explicitly to AWS.

On top of that, our local test env is based on docker-compose so it often has issues matching exactly to the deployed env in the cloud once you add all the networking.

I've wanted to start moving us to Kubernetes so we can have a much closer env across the board. In order to do this, we would need to support both osx and Linux development, and for this I was investigating minikube but my previous XP with minikube left me not liking that solution long term.

I look forward to investigating this tool and seeing the potential in a local development workflow.

[CameronNemo]

I blogged about using Linux containers on macOS, including research into the operation and features of solutions like minikube, lima/nerdctl, Rancher Desktop, and Docker Desktop. You may find it helpful.

https://cameronnemo.gitlab.io/posts/mac-os-containers/

[btreecat]

Thank you, I will check it out

[rodgerd]

> we basically have recreated k8s only more expensive and fragmented

Exactly my driver for getting k8s (in the form of OpenShift) in place years ago to support a microservices push: if you want to deploy a fleet of a few hundred independent runtimes independently of one another, you could waste a lot of time and effort building everything that's needed to support that out of bits of VMware and F5 irules and things, or you can use something designed to support the case from day one.