zshrc file and just stopped using docker desktop altogether.

It works so well I added the eval command to my. (or any other docker command for that matter) as usual. Here’s an image of Lens with my local cluster running 25+ containers (though you’d have to take my word that the machine is quiet :) )Īt this point you can kubectl deploy anything that is already existing – but what do you do if you want to deploy an image created locally? well, that’s not complicated either you need to build the image on the docker minikube is using : eval $(minikube docker-env) Tada working Kubernetes without all the fan-fare (pardon the pun). If you like you can also define the resources for the minikube image before you start it up minikube config set cpu Last month I went through the whole new computer setup thingy (you know, the important stuff, like setting up a development font, themes for all editors etc :) ), I also decided to see if I can get Kubernetes running without paying the noise-tax – and it seems that its doable with couple of simple steps: Luckily, most of the time I have access to remote Kubernetes servers so I rarely used the option but whenever I did (re)try it, I quickly tuned it back off. That looks good on paper and technically it works but not without a price… (at least on my Mac) it also comes with fans a-blazing and the soundtrack of a 747 taking off. I don’t remember exactly when, Docker desktop added support for running Kubernetes. It works pretty well, good even for almost everything. Like most people I’ve been using Docker Desktop for a lot of years to get my fix for container. MacOS is a Unix but it isn’t a Linux so, unfortunately, if/when we need to use linux-y things like docker we need to install a VM just like in the Windows world. Edit June 2023: Added a section on Colima

Brew install docker engine