

❯ hyperkit -v hyperkit: 0.20200908 Homepage: License: BSD Install Docker CLI Hyperkit is still a viable choice for local Kubernetes clusters on Mac. If you didn’t use Homebrew, then uninstall the tool accordingly. This will get rid of not just Docker but also Hyperkit, Docker daemon which allows building images, Docker CLI to interact with the daemon, Kubernetes clusters and kubectl binary (unless you have it deployed separately).

Let’s start with removing Docker Desktop first. If you have tried this on Linux, let me know how it went.Īre you on Apple M1 Silicon (ARM64)? Jump to the end of the post for M1 specific instructions. With the “in-your-face” popup to force upgrade Docker and the software license change, it was time to look elsewhere for local Kubernetes development needs. Even though it eats CPU and memory like crazy and makes the fans go wild.

I have been using Docker Desktop to enable Docker and Kubernetes in Mac for quite some time now.
