So, my migration journey had different steps: So, that means that some of my containers also need to be moved to the new platform to avoid any data loss. Because I’m not a pure docker usage, I don’t follow sometimes the thing to have your container stateless and using volumes especially when you are doing a small use for some time and that’s it. So, the only thing I need to do is migrate my images and containers. So, after enabling that and restarting my Rancher Desktop, I can type my commands as you can see in the picture below: Maybe in the future, you want to move away from everything resembling docker even at the client-side and move to a Containers kind of approach, but for now, what I needed is to simplify the process. ) so it will smooth a lot of the transition. This is not enabled by default, but it is very easy to do it and it will make you not need to change all your “docker-like” commands (docker build, docker ps. And the first thing you will notice is that you can configure Docker Desktop to be compliant with the Docker CLI API as you can see in the picture below.

So, by default we will have a Kubernetes environment running in our system, and we can even select the version of that cluster as you can see in the picture below:īut also in Rancher, they noticed the opportunity window they have in front of them, and they were very aggressive in providing an easy migration path from Docker Desktop. The main difference with Docker Desktop is that Rancher Desktop is built with Kubernetes in mind and for Docker Desktop, that came as an afterthought. So I installed the Rancher Desktop 1.0.0 on my Mac and the installation was very, very easy. The idea here is to talk more about the journey of that migration. Built images are immediately available to use in your local workloads without any pushing, pulling, or copying. It uses the same container runtime as Kubernetes. Container management to build, push, and pull images and run containers.

Docker on mac without desktop