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!
@elkbullwinkle2 жыл бұрын
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.
@SchoolofDevops2 жыл бұрын
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/
@harshithrao82482 жыл бұрын
@@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
@olympusbiz95832 жыл бұрын
From last 15 days I was trying to install kubeadm with docker.........now I get to know the story
@user-ov8tt8oz2y5 ай бұрын
simple and very nice explanation
@daimonos4182 жыл бұрын
I didn't know about dockershim! Thank you : )
@eswarreddy82642 жыл бұрын
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__2 жыл бұрын
Awesome! many thanks
@Ky-vv8nj2 жыл бұрын
I wonder how this affects TrueNAS SCALE, since they are using K3S with docker containers.
@vikasthorat85152 жыл бұрын
Docker images is always will get use in kubernates and and container D instead of Container Run will use!!!!
@mlguy83762 жыл бұрын
Really interesting. Saved me thinking about a future epic.
@zahurulhaque63772 жыл бұрын
Awesome explanation, nailed it bro
@kps26422 жыл бұрын
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
@amchourasia2 жыл бұрын
Thanks for this video
@denniscook96642 жыл бұрын
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?
@SpencerWilliamsIV2 жыл бұрын
I'm looking at Docker Desktop right now and it says version 1.24.2
@AaronBish2 жыл бұрын
Use Rancher Desktop. It doesn't have the new licensing burdens that Docker Desktop does.
@ZeeshanKhan-id4fw2 жыл бұрын
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 ?
@nroose2 жыл бұрын
This is so so silly and misleading and long winded. This whole thing was overblown. Please take this down. It's just misleading.
@lukasmakac2 жыл бұрын
Can you be more specific ?
@nroose2 жыл бұрын
@@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.
@SchoolofDevops2 жыл бұрын
@@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.
@utkarshdharmadhikari68162 жыл бұрын
I guess only the title is confusing, rest video is very well explained.
@dominusbelial2 жыл бұрын
Title is just a bit baity
@van_tigranyan2 жыл бұрын
Actually that happened a year ago.
@sunidhinayak6413 Жыл бұрын
Sir How to register for your sessions ?
@puneetsingh362 жыл бұрын
You could have mentioned about cri-dockerd.
@SchoolofDevops2 жыл бұрын
Yes I should have. I will probably make another video explaining it.
@klawtawar2 жыл бұрын
Very nice 👍
@petereriksson89152 жыл бұрын
Nothing happens, just switch the container runtime.
@venkatesanr94552 жыл бұрын
Can anyone suggest online linux practicing environment which also helps to learn docker as a beginner please.
@thasin96712 жыл бұрын
Official docker webpage has docker lab.
@SchoolofDevops2 жыл бұрын
@@thasin9671 it can be accessed using labs.play-with-docker.com/
@ericjdevops2 жыл бұрын
Thanks
@AnkitKumar-ow6fg2 жыл бұрын
Will it be worth learning docker now ?
@Huskymoonmoon2 жыл бұрын
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.
@drgr33nUK2 жыл бұрын
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.