You might recall a little bit ago when we were first talking about Docker.
We introduced a couple of different really important commands.
So he spoke about say Docker P.S. and exact and logs and I had said that these were really important
commands because we started learning about Cuban cities a lot these commands translate directly into
the Cuban 80s world.
So we're gonna see that in action in this diagram right here.
I've got a couple of commands from the docker world and then they're equivalent over in the community's
world chamber Docker in general is just about running individual containers divinities is about running
a bunch of containers together once you start making use of Cuban eddies.
We're not really going to use the docker command line tool much anymore.
Instead we're going to use the command line tool that we use to interact with Cuban eddies which is
cube CTO so just as we have a command to list out all of our running containers we have something very
similar in the commodities world for listing on all of our different pods.
We've got something in Docker for running a command inside of a container.
Same thing for Cuban cities.
We have something for printing out logs tied to a container.
Same thing for Cuban natives and then of course there's a couple of others that we need to be aware
of as well so in this video we're going to very quickly run through all the commands you see right here.
First thing I'm going to do is show you once again how we can create a pod.
We do so by processing a config file but no I'm not starting out off at the very top.
Let's just jump down here to the towards the bottom so to process a config file and create all the pods
designated inside there.
We use cube GTL apply dash F and then the name of the config file.
It's going to do that again really quickly inside my k AIDS directory.
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
then list out all the different pods with Cube CDL get pods.
I'll do that right now.
There's the pod right there it is running I can run a command inside that pod by using that cube CDL
exactly Dash I t then the name of the pod and the command to execute inside their.
So for example we could start up a shell inside of a container that is being ran inside of a pod lot
of qualifiers and that sentence with Cube Seitel exact I.T. than the name of the pod which is post and
then the command that we want to run.
So in this case I could open up a shell with S H and there we go.
I've got a shell open inside of the container inside that pod.
Now remember a pod can technically run more than one container inside of it at a time if you ever are
running multiple containers inside a pod and run this exact command cube CTO will prompt you and ask
you which container you want to run that command inside of.
But again you and I were only ever going to run one container inside of pod at a time.
So we don't really have to worry about that scenario.
Once we're all done we can hit exit and get back to our command line.
Next up to get all the logs out of a pod will run keeps the logs and the pod name the cubes GTL logs
those and there's all the logs all right just a couple of more very quickly if we ever want to delete
a pod manually for some reason most common reason you'll do this is if you want to manually restart
a pod will do keeps TTL delete pod and then the name of it.
So for example UCL delete pod hosts when you run delete it might take a couple of seconds for the deletion
to actually be processed all the way up to 10.
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
a get pods and we'll see there are no pods and then we can't recreate that pod very quickly by doing
another apply dash f those GMO.
Now I could do another get pods and the pod is now there again.
And then finally gives still.
Describe pod.
So this will print out some information about the pod itself.
Most importantly it's going to tell us or give us some debug information if we feel as though something
is going wrong with the pod.
So we could do a QVC DL describe od those I'll run that and then we'll see some information here that's
kind of all gibberish right now.
But most importantly down here at the bottom is a event log.
So something is going wrong with a pod you will very quickly want to describe the pod and take a look
at the events list and this will tell you about some stuff that is going on with the pod and hopefully
give you some debug information OK.
So that's it.
That's a couple of very common QCT l commands.
We're going to keep these commands in our back pocket because we're going to use them quite a bit as
we start to work with Cuban eddies more and more.
Let's pause right here and continue in just a minute.