How Kubernetes works under the hood with Docker Desktop
1–10 of 13 posts
Re: How Kubernetes works under the hood with Docker Desktop
#2Running Windows on my laptop I got really confused with Windows docker, docker desktop, wsl docker, docker in a Linux VM. In the end I stuck with WSL Docker as it was the closest to Linux while still native, but its a mess.
Re: How Kubernetes works under the hood with Docker Desktop
#3Running Windows on my laptop I got really confused with Windows docker, docker desktop, wsl docker, docker in a Linux VM. In the end I stuck with WSL Docker as it was the closest to Linux while still native, but its a mess.
Windows docker allows you to run windows in a docker container.
Docker desktop is just the windows interface and GUI for docker.
Docker in a VM is usually a stop gap for windows systems that can't run Linux in hyper-v.
Docker in WSL simply runs the docker containers in WSL rather than in hyper-v or a VM.
Re: How Kubernetes works under the hood with Docker Desktop
#4This is one of the main reasons for what i could keep using Docker desktop
Re: How Kubernetes works under the hood with Docker Desktop
#5This is one of the main reasons for what i could keep using Docker desktop
I think Rancher Desktop is a capable replacement for local Kubernetes development if you are ever looking to change.
Re: How Kubernetes works under the hood with Docker Desktop
#6I really dislike this approach to Kubernetes. The stated aim is to "hide the complexity" but the real goal seems to be making you dependent on docker desktop.
This is fine while you are in development and only doing local testing. What happens when you want to deploy to a cloud service and something goes a bit wrong? You are much better off slogging through the underlying setup, without the crutches, and knowing exactly what is going on.
At least that way you will have a basic understanding of what it will take to move your project off your workstation and onto some kind of public facing infrastructure.
Re: How Kubernetes works under the hood with Docker Desktop
#7I really dislike this approach to Kubernetes. The stated aim is to "hide the complexity" but the real goal seems to be making you dependent on docker desktop. This is fine while you are in development and only doing local testing. What happens when you want to deploy to a cloud service and something goes a bit wrong? You are much better off slogging through the underlying setup, without the crutches, and knowing exac…
If you're going to deploy to a cloud service you are likely going to use the Kubernetes service provided by the cloud. EKS, AKS, GKE, etc. You don't need to slog through anything with those.
Most people aren't going to be Kubernetes operators and will use the tools that are easy for them so they can focus on what they are doing (which isn't about operating a cluster).
Time is finite and most people don't have the job of being Kubernetes experts. They are spending their time using it to do something else. Managed tools make it possible for them to spend more time on what's important to them.
Re: How Kubernetes works under the hood with Docker Desktop
#8Running Windows on my laptop I got really confused with Windows docker, docker desktop, wsl docker, docker in a Linux VM. In the end I stuck with WSL Docker as it was the closest to Linux while still native, but its a mess.
Windows docker allows you to run windows in a docker container. Docker desktop is just the windows interface and GUI for docker. Docker in a VM is usually a stop gap for windows systems that can't run Linux in hyper-v. Docker in WSL simply runs the docker containers in WSL rather than in hyper-v or a VM.
Docker in WSL does run a hyper-v VM.
Re: How Kubernetes works under the hood with Docker Desktop
#9I really dislike this approach to Kubernetes. The stated aim is to "hide the complexity" but the real goal seems to be making you dependent on docker desktop. This is fine while you are in development and only doing local testing. What happens when you want to deploy to a cloud service and something goes a bit wrong? You are much better off slogging through the underlying setup, without the crutches, and knowing exac…
If you're going to deploy to a cloud service you are likely going to use the Kubernetes service provided by the cloud. EKS, AKS, GKE, etc. You don't need to slog through anything with those. Most people aren't going to be Kubernetes operators and will use the tools that are easy for them so they can focus on what they are doing (which isn't about operating a cluster). Time is finite and most people don't have the job…
Well, yeah, but how do you move from Docker Desktop kubernetes to something like AKS?
Some time back, one of the things stopping me from migrating off Visual Studio was that I had been relying on the integrated tools to help with deployment of my small system. I came to the sudden realisation that I had no idea exactly what to do to deploy something like a lambda function or a container into ECS, because it was being done for me by the AWS Visual Studio toolkit.
It's kind of dangerous in lots of ways. You have little idea of security contexts, of how the different parts interact, of what you might be accidentally exposing to the general internet. It's like anything that demos well: it hides all the stuff you need to know about at the expense of trying to get you started quickly. Hiding all the dodgy decisions the wizard makers make will get you burned.
In the end, I would have been much better off learning the AWS CLI - I ended up having to do it anyway to utilise a github action to do my deployments.
At the very least, these tools should spit out the commands they are running in some kind of ordered fashion so you can "play along". Long term, the hand-holding is counter productive for most developers.
Re: How Kubernetes works under the hood with Docker Desktop
#10I like kind, its great. But you still need a docker daemon and on a mac docker desktop is still king.