Kubernetes Stops Supporting Docker with v1.24. What Happens Now ?

[@muhidcs]

I'm studying DevOps as a course in my University and this video helped me SO MUCH to understand runtimes and CRI. Hats off to the explanation!

[@elkbullwinkle]

What was worth mentioning is that it's going to affect folks who run their CI\CD like jenkins in a kubernetes cluster and use docker for building images which usually just means sharing a docker daemon with the container (which is most common scenario really), now they'd have to come up with an alternative way.

[@SchoolofDevops]

Good point Sasha. Its definitely worth mentioning. However, to add my two cents, using docker to build images from a CI has never been a good idea, since the beginning of time. It requires you to provide root access (docker daemon runs with root access always, no way around it). If if you do not intentionally do it, it happens automatically as it uses sticky bit. Also it leads to a more complex setup. What you should be using instead is Kaniko, an alternative image builder, which runs from within a container, requires no root access, takes Dockerfile as an input, builds an image and also publishes it. Its a project created by Google and my favourite tool to use with any CI Platform. github.com/GoogleContainerTools/kaniko . I have been guilty of using Docker in past with Jenkins, but have been moving my content to use Kaniko lately. Other tool to consider would be buildah, a project created by RedHat folks. buildah.io/

[@harshithrao8248]

@@SchoolofDevops I use azure devops pipeline CI/CD to build docker images and push to azure container registry and then use the kubectl restart to pull the latest image, but as i have seen azure kubernetes uses containerd as runtime does this change also affect me in any way?

[@msajjadm78]

A great piece of work. Thumbs up for you sir.

[@gouravshahj]

Thanks @Wah IT

[@olympusbiz9583]

From last 15 days I was trying to install kubeadm with docker.........now I get to know the story

[@user-ov8tt8oz2y]

simple and very nice explanation

[@daimonos418]

I didn't know about dockershim! Thank you : )

[@eswarreddy8264]

Thank You for the detailed explanation

[@sameersrivastava4117]

Very well explained. Thanks 👍

[@MisfitToy]

So if I'm starting out should I skip Docker altogether and just use containerd with Kubernetes?

[@ShaileshYadav__]

Awesome! many thanks

[@Ky-vv8nj]

I wonder how this affects TrueNAS SCALE, since they are using K3S with docker containers.

[@vikasthorat8515]

Docker images is always will get use in kubernates and and container D instead of Container Run will use!!!!

[@mlguy8376]

Really interesting. Saved me thinking about a future epic.

[@zahurulhaque6377]

Awesome explanation, nailed it bro

[@kps2642]

great video!

[@Kannavolgs37]

Can anyone help me to solve my dought I deployed ngnix application inside a kubernetes pod. It is working in localhost mechine but I will try to access with different computer and my mobile with different networks in world. How can I access my application in different computer instead of my localhost. Please comment answer for clear explanation

[@SR-ti6jj]

Take a look at ngrok my friend

[@amchourasia]

Thanks for this video

[@denniscook9664]

What will this mean for Kubernetes found in the Docker for Desktop. I see it is still version 1.21. Will it just remain a version below 1.24?

[@SpencerWilliamsIV]

I'm looking at Docker Desktop right now and it says version 1.24.2

[@AaronBish]

Use Rancher Desktop. It doesn't have the new licensing burdens that Docker Desktop does.

[@ZeeshanKhan-id4fw]

I have questions related to kubernetes volume How can we copy file or folder 📂 into persistent volume before attaching persistent volume to pod or container??any suggestion

[@SchoolofDevops]

The best way to do this in my opinion is to use initcontainers. These are the containers that are launched for specific jobs such as copying over files to a volume, before actual application container is launched. Since this init container is part of the same pod, it has access to the same volume as well. Have you considered using initContainers ?

[@nroose]

This is so so silly and misleading and long winded. This whole thing was overblown. Please take this down. It's just misleading.

[@lukasmakac]

Can you be more specific ?

[@nroose]

@@lukasmakac Many people continue to build their images with Docker and run them on Kubernetes. It's not stopping support for Docker, it's stopping support for building docker images in a specific way. This title and all the crap like it are knowingly misleading and alarmist click bait.

[@SchoolofDevops]

@@nroose It is already explained in the video that you would still continue using docker in dev and to build images, and then run those with kubernetes. The title is because most people are wondering why kubernetes stopped supporting docker. That is true in one way, false in other. Thats what this video explains.

[@utkarshdharmadhikari6816]

I guess only the title is confusing, rest video is very well explained.

[@dominusbelial]

Title is just a bit baity

[@van_tigranyan]

Actually that happened a year ago.

[@sunidhinayak6413]

Sir How to register for your sessions ?

[@puneetsingh36]

You could have mentioned about cri-dockerd.

[@SchoolofDevops]

Yes I should have. I will probably make another video explaining it.

[@klawtawar]

Very nice 👍

[@petereriksson8915]

Nothing happens, just switch the container runtime.

[@venkatesanr9455]

Can anyone suggest online linux practicing environment which also helps to learn docker as a beginner please.

[@thasin9671]

Official docker webpage has docker lab.

[@SchoolofDevops]

@@thasin9671 it can be accessed using labs.play-with-docker.com/

[@ericjdevops]

Thanks

[@AnkitKumar-ow6fg]

Will it be worth learning docker now ?

[@Huskymoonmoon]

It still worthy because in the container world Docker still dominates the market, thus K8S drop support for dockershim, the reason to drop it is not on the popularity but on the maintainability, they need a single interface to interact with the container engine.

[@drgr33nUK]

Sure, learning Docker will teach you everything you need to know. The changes are just a shift away from Docker branding everything. From a user perspective, everything works the same.

[@AnkitKumar-ow6fg]

@@Huskymoonmoon Thanks for the help

[@AnkitKumar-ow6fg]

@@drgr33nUK Thanks for the help.