How to Install & Configure Rancher-Desktop on Windows (How to Run Docker & Kubernetes on Windows)

In this video we will learn how to install Rancher-Desktop on windows OS and configure WSL2 (Windows sub Linux) to let us run Docker containers and also manage them by Kubernetes and also it is a good replacement for Docker-Desktop.

Rancher Desktop is an all-in-one solution for container management on your desktop workstation. It provides an easily maintained Kubernetes installation that runs on your local windows machine and streamlines setting up containerized workflows in development as a Linux Dev Environment on Windows with WSL 2.

How does Rancher Desktop differ from Docker Desktop?
Choose the version of Kubernetes you want
Test how workloads handle Kubernetes upgrade
Choose between Containerd and Dockerd
Run stand-alone containers
Build, push, and pull container images
Simple Kubernetes Configuration
Run Docker containers on windows in easy way

==========================================
==========================================

🔗Enable the Windows Subsystem for Linux
🔗Enable Virtual Machine feature
🔗Set WSL 2 as your default version
wsl --set-default-version 2
🔗check the wsl version
wsl -l -v
🔗 Solve Docker permission from the following resource:
sudo addgroup --system docker
sudo adduser $USER docker
newgrp docker
# And something needs to be done so $USER always runs in group `docker` on the `Ubuntu` WSL

"But the main command is this one:

WSL2
rancher desktop
kubernetes
docker
docker cli
docker on windows
kubernetes on windows
kubernetes locally
windows subsystem for Linux

Like | Share | Subscribe | Follow

[lolomimama]

Thank you very much. I tried to do an installation on my own but I didn't manage to get it to work. With your guide I could finally have it running in less than an hour.

[AndreBellCopywriter]

Thanks for the detailed instructions and thanks for listing the longer steps in the description. Followed all the steps exactly and in order. Each step said installed successfully. But wsl -l lv says: "*Windows Subsystem for Linux has no installed distributions.*"
So I tried 'wsl --update' and it said updating to version 2.2.24. Afterward I ran 'wsl -l -v' and was told, "*wsl : The term 'wsl' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.*" Arggg. Going to try using my admin login, instead of run as admin. Anyhow, is a problem on my end. Thx x2 for the steps.

[peanut-d-cat]

thank you so much. it really helped me on my job.

[rajesht]

much informative video. Thank you for sharing your knowledge

[thewarrior]

a new follower from France. I do love your work. keep doing. tks a lot

[LaxmanMerupula]

Thank you so much ... I appreciated your help

[maddi]

It's wonderful. can you post next steps also please.

[MatteoMi]

A video I've found on google tells me to run a search on google to find the solution of the problems he founds! :D Right, kidding (just a bit, would make a video a lot shorter if you just show the solution without the search:) but still well explained and interesting 👍

[Mr.rawJat]

I get below error, please help.

$ docker version
Client:
Version: 23.0.1-rd
API version: 1.42
Go version: go1.19.5
Git commit: 393499b
Built: Fri Feb 10 16:55:36 2023
OS/Arch: linux/amd64
Context: default
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Running
$ sudo dockerd
gives below error:
failed to initialize a tracing processor "otlp" error="no OpenTelemetry endpoint: skip plugin"

...
grpc: addrConn.createTransport failed to connect to <nil> 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial timeout". Reconnecting... module=grpc
failed to start daemon: Error initializing network controller: error obtaining controller instance: unable to add return rule in DOCKER-ISOLATION-STAGE-1 chain: (iptables failed: iptables --wait -A DOCKER-ISOLATION-STAGE-1 -j RETURN: iptables v1.8.7 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain DOCKER-ISOLATION-STAGE-1
(exit status 4))