Now let's go ahead and create a board manually.
And for that we could utilize command, which is similar to Docker run command.
But with Docker Run Command, you could create just a single Docker container here.
You could utilize Cube still run command in order to create just a single port.
Let's do that cube.
It'll run here will be named.
Let's for instance utilize engine x docker image which is available at Docker Hub.
For that let's enter here name of the port engine x and afterwards let's add option image and this value
will be in Genesis.
And Genesis here is name of the Docker image which will be pulled automatically and new container will
be created based on this image and this container will be running inside of the Kubernetes port.
Let's go ahead and see what will happen.
It'll run again.
X does this image equals sign and genesis and here I see output port and Genesis created.
Let's enter command cube.
It'll get ports and here I see now single port and Genesis.
It is not yet ready and its status is container creating Let's enter same command again you still get
ports and now I see that this port is now run.
It is ready and its status is run.
Of course it took some time in order to create such a port because inside of it there was engine is
container and docker inside of the Kubernetes node was actually requested to pull engine x image from
Docker Hub and create corresponding container based on such image and Genesis.
Let's now find out details of this specific port with name and Genesis.
This name, we specify it manually here.
For that, please enter command cube.
Still describe port and here we'll be name of the port which you would like to describe.
Get details about here.
We'll be in Genesis.
It is name of the running port and here are many different details related to this specific port.
Let me scroll a bit up and here I'll find out such information as a namespace this port belongs to and
it was automatically assigned to default namespace.
That's why we were able to see it in the list when we entered command cubes.
It'll get port because such command lists all ports inside of the default namespace.
Here is information about node where such specific port was created or kept that Kubernetes automatically
distributes load across all nodes work and nodes inside of the cluster, and it selects specific node
for specific port.
And that's information about the node where this particular port was created.
In our single node cluster, of course, you will see the same node each time when you create any port
and here is IP address of such node.
Here is start time here all labels status is running and here is IP address which was assigned to this
particular port 170 217 zero three But please note that now we will not be able to connect to this particular
port using such internal IP address of the port.
In order to be able to connect to ports, you have to create services in Kubernetes, and that's what
we will look at a bit later here.
Below, you could also find out which containers were created inside of this port.
And there was just a single container.
Here is ID of such container.
Here was long ID here was image which was utilized for this particular container and that's that image
which we specified using this dash image option when we created new port.
Here is image ID and it is ID of the image from the Docker hub because by default, Kubernetes pulls
all images from the Docker hub.
Of course, it's possible to configure Kubernetes to pull images from other repository hosting services,
but default is Docker hub.
All right.
This are details about this particular port.
And we find out that there was IP address assigned to this board.
There was a container which was created inside of this port.
And here are logs related to creation of this particular port.
You see that this particular port was successfully assigned to mini cube node here with message about
pulling image and Jennings from the Docker hub.
Successfully pooled image, created container engineers and started container and Genesis.
And it means that now there is engine is container running inside of the created port.
Again, you could find the list of all ports by entering command cube CTL get ports.
And here was a single port available right now in the default namespace.