1
00:00:04,620 --> 00:00:11,190
We are done with the main practical part of this course and one step left and I would like to demonstrate

2
00:00:11,190 --> 00:00:18,660
to you how to change container runtime, which is currently Docker in our Kubernetes cluster to other

3
00:00:18,660 --> 00:00:22,800
container runtime, for instance, scenario or container D.

4
00:00:23,250 --> 00:00:31,320
And in order to modify container runtime, we need to delete current mini cubes set up and create new

5
00:00:31,320 --> 00:00:31,800
one.

6
00:00:32,549 --> 00:00:37,830
For that, let's go to the terminal here and let's enter mini cube status command.

7
00:00:39,360 --> 00:00:41,280
Now it is running Cuba.

8
00:00:41,280 --> 00:00:42,000
That is running.

9
00:00:42,040 --> 00:00:43,500
It is running.

10
00:00:43,800 --> 00:00:45,180
Let's not stop.

11
00:00:45,300 --> 00:00:46,140
Mini cube.

12
00:00:46,170 --> 00:00:47,490
Mini cube, stop.

13
00:00:48,660 --> 00:00:50,400
Stopping node mini cube.

14
00:00:52,130 --> 00:00:58,280
One Lord was stopped and now let's delete current set up mini cube delete.

15
00:01:00,630 --> 00:01:06,660
The little mini cube in VirtualBox, in my case, removed all traces of the mini cube cluster.

16
00:01:06,900 --> 00:01:09,660
Now let's create cluster over again.

17
00:01:09,690 --> 00:01:11,910
Mini cube start.

18
00:01:12,450 --> 00:01:19,030
I will again use driver option and its value will be a virtual box in my case.

19
00:01:19,050 --> 00:01:25,440
If your Windows user used to type here Hyper-V same as for previous mini cube start.

20
00:01:25,800 --> 00:01:30,450
But please notice that Docker option did not work for me.

21
00:01:30,450 --> 00:01:38,040
At least I wasn't able to run Siri or containers inside of the Docker container, so for some reason

22
00:01:38,040 --> 00:01:38,880
it didn't work.

23
00:01:39,030 --> 00:01:45,490
Therefore I utilize view toolbox and I don't recommend you to use now driver docker.

24
00:01:45,510 --> 00:01:50,520
So driver is VirtualBox in my case and next I will add option.

25
00:01:50,550 --> 00:01:56,700
There's this container, this runtime and this value will be Siri.

26
00:01:56,730 --> 00:01:57,270
Dash.

27
00:01:57,270 --> 00:01:57,780
Oh.

28
00:01:58,760 --> 00:02:01,700
One more option is container rd.

29
00:02:03,230 --> 00:02:05,540
You could try both if you want to do so.

30
00:02:05,630 --> 00:02:08,000
So I will enter here, I say.

31
00:02:08,000 --> 00:02:08,220
Right.

32
00:02:08,690 --> 00:02:09,410
Like that.

33
00:02:09,410 --> 00:02:13,930
And let's create a mini cube cluster from scratch once again.

34
00:02:13,940 --> 00:02:17,510
But now container runtime is set to zero.

35
00:02:18,530 --> 00:02:19,490
Let's go ahead.

36
00:02:21,050 --> 00:02:22,610
Start in control plane node.

37
00:02:22,610 --> 00:02:24,500
Mini cube in cluster mini cube.

38
00:02:24,500 --> 00:02:26,630
Again creating virtual box.

39
00:02:27,660 --> 00:02:29,010
It will take a while.

40
00:02:30,660 --> 00:02:34,260
Now I see step repair and Kubernetes on Creole.

41
00:02:35,950 --> 00:02:37,550
And finally it was done.

42
00:02:37,570 --> 00:02:39,370
Let's now check status.

43
00:02:39,400 --> 00:02:41,380
Mini cube status.

44
00:02:43,450 --> 00:02:45,610
Diet control plane host is running.

45
00:02:45,610 --> 00:02:53,050
Everything is running same as before, but now contain a runtime inside of the node is zero.

46
00:02:53,080 --> 00:02:54,520
Let's check that.

47
00:02:54,820 --> 00:03:05,320
Let's switch to mini cube IP address and let's enter here first mini cube IP and sage docker at 192

48
00:03:05,320 --> 00:03:10,240
160 859 102 Yes.

49
00:03:10,780 --> 00:03:16,450
DC User Now I'm inside of the mini cube node and now let's enter Docker.

50
00:03:16,450 --> 00:03:21,010
PS And what I see, I see cannot connect to the Docker.

51
00:03:22,760 --> 00:03:30,650
And it is an indication that Docker is not running inside of this node because we are using cry o container

52
00:03:30,650 --> 00:03:31,910
runtime instead.

53
00:03:32,660 --> 00:03:40,640
But how to check whether there are serial containers where easily using following command sudo siri

54
00:03:40,670 --> 00:03:46,640
ctrl v s and here are a bunch of different containers which are running.

55
00:03:47,660 --> 00:03:52,910
Like you proxy or DNS storage provision and so on.