We are done with the main practical part of this course and one step left and I would like to demonstrate
to you how to change container runtime, which is currently Docker in our Kubernetes cluster to other
container runtime, for instance, scenario or container D.
And in order to modify container runtime, we need to delete current mini cubes set up and create new
one.
For that, let's go to the terminal here and let's enter mini cube status command.
Now it is running Cuba.
That is running.
It is running.
Let's not stop.
Mini cube.
Mini cube, stop.
Stopping node mini cube.
One Lord was stopped and now let's delete current set up mini cube delete.
The little mini cube in VirtualBox, in my case, removed all traces of the mini cube cluster.
Now let's create cluster over again.
Mini cube start.
I will again use driver option and its value will be a virtual box in my case.
If your Windows user used to type here Hyper-V same as for previous mini cube start.
But please notice that Docker option did not work for me.
At least I wasn't able to run Siri or containers inside of the Docker container, so for some reason
it didn't work.
Therefore I utilize view toolbox and I don't recommend you to use now driver docker.
So driver is VirtualBox in my case and next I will add option.
There's this container, this runtime and this value will be Siri.
Dash.
Oh.
One more option is container rd.
You could try both if you want to do so.
So I will enter here, I say.
Right.
Like that.
And let's create a mini cube cluster from scratch once again.
But now container runtime is set to zero.
Let's go ahead.
Start in control plane node.
Mini cube in cluster mini cube.
Again creating virtual box.
It will take a while.
Now I see step repair and Kubernetes on Creole.
And finally it was done.
Let's now check status.
Mini cube status.
Diet control plane host is running.
Everything is running same as before, but now contain a runtime inside of the node is zero.
Let's check that.
Let's switch to mini cube IP address and let's enter here first mini cube IP and sage docker at 192
160 859 102 Yes.
DC User Now I'm inside of the mini cube node and now let's enter Docker.
PS And what I see, I see cannot connect to the Docker.
And it is an indication that Docker is not running inside of this node because we are using cry o container
runtime instead.
But how to check whether there are serial containers where easily using following command sudo siri
ctrl v s and here are a bunch of different containers which are running.
Like you proxy or DNS storage provision and so on.