A Getting started discussion with Docker Desktop vs. Rancher Desktop

I saw a post a few months ago about Rancher Desktop.  Until that time, I'd never ever heard of the thing.  From my uninitiated viewpoint, Rancher Desktop looks like Docker Desktop, except specific for Kubernetes. Thinking that's all it was, I stopped reading any more.  I'm already working hard to understand all the nuances of the Docker engine outside of the Desktop application.

But then I came upon an article by Matt Farina (t|g|l) entitled, "Docker Desktop vs Rancher Desktop | Code Engineered." Matt is good about saying that he's a member of the Rancher Desktop team, but the feature comparison chart still got me thinking.

Feature Comparison of Docker Desktop vs. Rancher Desktop

Now I'm thinking to myself, "Maybe you shouldn't be working so much with Docker Desktop as you get started."

Can someone help me navigate out of this analysis paralysis?

Parents
  • There's not really a downside to using Rancher Desktop out of the gate. Just use the Moby (oss docker) option to get standard docker commands. The kubernetes portion is optional. I initially switched to it for better WSL+kubernetes integration, but now it's just a standard for our devs. Something not really mentioned was the inclusion of Traefik out of the box for the devs has been great to get them out of localhost:port hell. Also great for devs growing into kubernetes, with parts of the rancher kubernetes dashboard built in.

Reply
  • There's not really a downside to using Rancher Desktop out of the gate. Just use the Moby (oss docker) option to get standard docker commands. The kubernetes portion is optional. I initially switched to it for better WSL+kubernetes integration, but now it's just a standard for our devs. Something not really mentioned was the inclusion of Traefik out of the box for the devs has been great to get them out of localhost:port hell. Also great for devs growing into kubernetes, with parts of the rancher kubernetes dashboard built in.

Children
No Data