1 00:00:00,990 --> 00:00:03,760 You might recall a little bit ago when we were first talking about Docker. 2 00:00:03,780 --> 00:00:06,530 We introduced a couple of different really important commands. 3 00:00:06,600 --> 00:00:11,760 So he spoke about say Docker P.S. and exact and logs and I had said that these were really important 4 00:00:11,760 --> 00:00:16,680 commands because we started learning about Cuban cities a lot these commands translate directly into 5 00:00:16,680 --> 00:00:17,850 the Cuban 80s world. 6 00:00:18,070 --> 00:00:21,180 So we're gonna see that in action in this diagram right here. 7 00:00:21,180 --> 00:00:26,220 I've got a couple of commands from the docker world and then they're equivalent over in the community's 8 00:00:26,220 --> 00:00:32,280 world chamber Docker in general is just about running individual containers divinities is about running 9 00:00:32,310 --> 00:00:36,110 a bunch of containers together once you start making use of Cuban eddies. 10 00:00:36,120 --> 00:00:39,500 We're not really going to use the docker command line tool much anymore. 11 00:00:39,510 --> 00:00:43,860 Instead we're going to use the command line tool that we use to interact with Cuban eddies which is 12 00:00:43,860 --> 00:00:49,700 cube CTO so just as we have a command to list out all of our running containers we have something very 13 00:00:49,700 --> 00:00:53,270 similar in the commodities world for listing on all of our different pods. 14 00:00:53,270 --> 00:00:56,630 We've got something in Docker for running a command inside of a container. 15 00:00:56,630 --> 00:00:58,000 Same thing for Cuban cities. 16 00:00:58,220 --> 00:01:00,590 We have something for printing out logs tied to a container. 17 00:01:00,590 --> 00:01:04,040 Same thing for Cuban natives and then of course there's a couple of others that we need to be aware 18 00:01:04,040 --> 00:01:09,290 of as well so in this video we're going to very quickly run through all the commands you see right here. 19 00:01:10,400 --> 00:01:14,100 First thing I'm going to do is show you once again how we can create a pod. 20 00:01:14,100 --> 00:01:18,740 We do so by processing a config file but no I'm not starting out off at the very top. 21 00:01:18,840 --> 00:01:24,720 Let's just jump down here to the towards the bottom so to process a config file and create all the pods 22 00:01:24,720 --> 00:01:26,040 designated inside there. 23 00:01:26,070 --> 00:01:30,610 We use cube GTL apply dash F and then the name of the config file. 24 00:01:30,620 --> 00:01:35,450 It's going to do that again really quickly inside my k AIDS directory. 25 00:01:35,450 --> 00:01:46,820 I'll do a cube Seitel apply dash f those who post dot e-mail and that's going to create the pod I can 26 00:01:46,820 --> 00:01:50,530 then list out all the different pods with Cube CDL get pods. 27 00:01:50,720 --> 00:01:53,530 I'll do that right now. 28 00:01:53,570 --> 00:02:00,450 There's the pod right there it is running I can run a command inside that pod by using that cube CDL 29 00:02:00,460 --> 00:02:06,670 exactly Dash I t then the name of the pod and the command to execute inside their. 30 00:02:06,680 --> 00:02:12,170 So for example we could start up a shell inside of a container that is being ran inside of a pod lot 31 00:02:12,170 --> 00:02:20,390 of qualifiers and that sentence with Cube Seitel exact I.T. than the name of the pod which is post and 32 00:02:20,390 --> 00:02:21,590 then the command that we want to run. 33 00:02:21,920 --> 00:02:25,610 So in this case I could open up a shell with S H and there we go. 34 00:02:25,610 --> 00:02:30,040 I've got a shell open inside of the container inside that pod. 35 00:02:30,070 --> 00:02:35,320 Now remember a pod can technically run more than one container inside of it at a time if you ever are 36 00:02:35,320 --> 00:02:40,660 running multiple containers inside a pod and run this exact command cube CTO will prompt you and ask 37 00:02:40,660 --> 00:02:43,610 you which container you want to run that command inside of. 38 00:02:43,780 --> 00:02:47,870 But again you and I were only ever going to run one container inside of pod at a time. 39 00:02:47,980 --> 00:02:49,720 So we don't really have to worry about that scenario. 40 00:02:50,690 --> 00:02:55,530 Once we're all done we can hit exit and get back to our command line. 41 00:02:55,590 --> 00:03:02,280 Next up to get all the logs out of a pod will run keeps the logs and the pod name the cubes GTL logs 42 00:03:02,700 --> 00:03:10,260 those and there's all the logs all right just a couple of more very quickly if we ever want to delete 43 00:03:10,290 --> 00:03:15,150 a pod manually for some reason most common reason you'll do this is if you want to manually restart 44 00:03:15,180 --> 00:03:18,570 a pod will do keeps TTL delete pod and then the name of it. 45 00:03:18,570 --> 00:03:27,350 So for example UCL delete pod hosts when you run delete it might take a couple of seconds for the deletion 46 00:03:27,350 --> 00:03:29,900 to actually be processed all the way up to 10. 47 00:03:29,990 --> 00:03:35,190 So if it hangs for about 10 seconds or so that's told you OK just let it do its thing we can then do 48 00:03:35,220 --> 00:03:41,770 a get pods and we'll see there are no pods and then we can't recreate that pod very quickly by doing 49 00:03:41,770 --> 00:03:46,300 another apply dash f those GMO. 50 00:03:46,340 --> 00:03:51,160 Now I could do another get pods and the pod is now there again. 51 00:03:51,360 --> 00:03:53,090 And then finally gives still. 52 00:03:53,100 --> 00:03:54,240 Describe pod. 53 00:03:54,240 --> 00:03:57,560 So this will print out some information about the pod itself. 54 00:03:57,570 --> 00:04:01,890 Most importantly it's going to tell us or give us some debug information if we feel as though something 55 00:04:01,890 --> 00:04:03,170 is going wrong with the pod. 56 00:04:04,020 --> 00:04:13,480 So we could do a QVC DL describe od those I'll run that and then we'll see some information here that's 57 00:04:13,480 --> 00:04:15,580 kind of all gibberish right now. 58 00:04:15,580 --> 00:04:18,400 But most importantly down here at the bottom is a event log. 59 00:04:19,030 --> 00:04:23,470 So something is going wrong with a pod you will very quickly want to describe the pod and take a look 60 00:04:23,470 --> 00:04:28,060 at the events list and this will tell you about some stuff that is going on with the pod and hopefully 61 00:04:28,060 --> 00:04:32,080 give you some debug information OK. 62 00:04:32,120 --> 00:04:32,600 So that's it. 63 00:04:32,630 --> 00:04:35,910 That's a couple of very common QCT l commands. 64 00:04:35,990 --> 00:04:39,560 We're going to keep these commands in our back pocket because we're going to use them quite a bit as 65 00:04:39,560 --> 00:04:41,900 we start to work with Cuban eddies more and more. 66 00:04:41,960 --> 00:04:43,850 Let's pause right here and continue in just a minute.