MacOS is Unix but not Linux so, unfortunately, if / when we need to use linux-y items as docker we need to install VM as in Windows world. This is true for the docker.
Like many people I have been using Docker Desktop for many years to set up a container. It works well, well even with almost anything. I can’t remember the exact time, Docker desktop added support for running Kubernetes. This looks great on paper and professionally works but at no cost … (probably on my Mac) it comes back with burning fans and the 747 song starts. Unfortunately, I often have the opportunity to connect to Kubernetes remote servers so I don’t like to use this method but when I try (try again), I stop it immediately.
Last month, I changed jobs and joined Kaltura – so I went through a very new computer programming process (you know, the basics, like setting up a development font, all editor edges and so on) –tax – and it seems possible with a few simple steps:
brew install hyperkit brew install minikube minikube start
if you want you can also specify the requirements for the mini-images before starting
minikube config set cpu <whatever> minikube config set memory <whatever>
tada used Kubernetes without all the fans (sorry the pun). Here’s a picture of the lens and my clusters with 25+ tools (though you should say the machine is silent :))
Get Docker running
In the meantime you can
kubectl deploy everything already exists – but what do you do if you want to use a local-made photo? well, it ‘s not difficult either if you want to create this image on the docker minikube is using:
eval $(minikube docker-env)
docker build -t <whatever> . (or any other docker rule in this regard) as usual.
It works very well and adds an eval command to my
.zshrc file and simply stop using docker desktop altogether.
Change of Docker Desktop license
Coda: A day or so ago, I saw it Docker is trying to make money from Docker Desktop and i want a business registration license, then this does not seem to be working properly (to me anyway) using hypekit + minikube can also be a good solution for devs who do not want / cannot afford to pay their pockets to pay for Registration so plus here.
if you remove docker desktop you need to install docker CLI which still uses the apache 2.0 license:
brew install docker
What about Podman?
A change of Docker Desktop license made this message popular. As I wrote above it seems that Docker CLI is still Apache 2.0 (at the time of writing :)), so there is no reason to stop, if granting permission is a reason to change.
That said, there is another whole solution to the Docker CLI called Podman. install it on MacOS and predict
brew install podman
Podman, like docker CLI needs linux VM to work with it if it runs mac. As usual minikube also has a podman installed on the VM that you can use via
eval $(minikube podman-env) – unfortunately, minikube has podman v.2.2.1 and the type that was added with brew is new (v.3.3.1) and does not match.
If you also want Kubernetes, as I want, I would have Docker CLI. if, however, you just need to make carriers – you can easily move to Podman – on the run
podman machine init # one time to download and setup a VM podman machine start
Podman appears to be compliant with the Docker CLI (though it adds a number of rules as well
system) that you can make / pull and so on.
One letter about making images with Podman: I tried to make my own Dockerfiles that I had with Podman and found the following error:Error: error making container build: modification of short but non-running names without TTY“. The point is that even if Docker thinks the images are coming from the docker hub randomly, you should share them with Podman, and edit
FROM apache/airflow:2.1.2 that
FROM docker.io/apache/airflow:2.1.2 has solved the problem