Now that we have a VCH deployed into the environement, it’s time we actually run some native docker commands and see if the containers are being created.
Observe that the Docker Engine here is linux based.
Browse through the vsanDatastore to see the files related to VCH that we deployed and an images folder is created, this is where all the images are pulled to when docker pull is run.
Now let’s pull an image from docker hub. When running docker native commands, we should always mention the host with -H as below. Now run couple of containers from the pulled busybox image.
docker -H 10.7.7.10.2376 --tls run busybox docker -H 10.7.7.10:2376 --tls run --name vmmaster busybox
To avoid specifying the values each time, we can actually set the VIC parameters as environment variables.
After having pulled the busybox image and punching in docker run, we see the containers running in the HTML client as below.
I did another ubuntu image pull. All the native commands are still good here. Below are a few of them
As discussed earlier, containers appear as running VMs in the virtual infrastructure. The container poweron and poweroff must not be done from VMware client. It is always managed from docker client using native commands.
Hope this was informative and helped you learn a bit about VMware Integrated Containers. Thanks!