This is part of a series of articles describing how to use the new features of vSphere Integrated Containers (VIC) v0.4.0. In previous posts, we have looked at deploying your first VCH (Virtual Container Hosts) and container using the docker API. I also showed you how to create some volumes to provide consistent storage for containers. In this post, we shall take a closer look at networking, and what commands are available to do container networking. I will also highlight some areas where there is still work to be done.
Also, please note that VIC is still not production ready. The aim of these posts is to get you started with VIC, and help you to familiarize yourself with some of the features. Many of the commands and options which work for v0.4.0 may not work in future releases, especially the GA version.
This video will show you the steps involved in deploying Apache Mesos on VMware’s Photon Controller product using the “cluster” mechanism available in Photon Controller. It uses Photon Controller CLI to create a tenant, resource ticket and a project. It then shows how to create an appropriate image for VMs to run Mesos, how to enable the Photon Controller deployment for Mesos clusters, and finally the creation of the cluster. After the deployment has succeeded, you are shown some command outputs and Photon Controller UI views of the running cluster. I decided to pick Mesos in this case, as I have already written a lot on Docker Swarm and Kubernetes, and have shown how to deploy these both natively, and using the Photon Controller “canned” cluster mechanism.
*** Note that at the time of writing, stand-alone Photon Controller is still not GA ***
*** Steps highlighted in this video may change in the GA version of the product ***
I decided to put together a very short video on VIC – vSphere Integrated Containers v0.4.0. In the video, I show you how to create your very first VCH (Virtual Container Host) and then I show you how you can create a very simple container using a docker API endpoint. I also show you how this is reflected in vSphere. Of course, VIC v0.4.0 is still a tech preview, and is not ready for production. Also note that a number of things may change before the VIC becomes generally available (GA). However, hopefully this is of interest to those of you who wish to get started with v0.4.0.
I mentioned yesterday that VMware made vSphere Integrated Containers (VIC) v0.4.0 available. Included in this version is support for container volumes. Now, as mentioned yesterday, VIC is still a work in progress, and not everything has yet been implemented. In this post I want to step you through some of the enhancements that we have made around docker volume support in VIC. This will hopefully provide you with enough information so that you can try this out for yourself.
I’ve been working very closely with our vSphere Integrated Container (VIC) team here at VMware recently, and am delighted to say that v0.4.0 is now available for download from GitHub. Of course, this is still not supported in production, and is still in tech preview. However for those of you interested, it gives you an opportunity to try it out and see the significant progress made by the team over the last couple of months. You can download it from bintray. This version of VIC is bringing us closer and closer to the original functionality of “Project Bonneville” for running containers as VMs (not in VMs) on vSphere. The docker API endpoint now provides almost identical functionality to running docker anywhere else, although there is still a little bit of work to do. Let’s take a closer look.
I would like to say a quick thank you for once again voting for my blog in the annual vBlog ballot. It is very humbling that so many of you voted for my blog. Once again I came in at position #3, surrounded by such luminaries as Duncan Epping, William Lam, Frank Denneman and Chris Wahl. And to top it off, I also came in as #1 in the Best Storage Blog category. To say I’m thrilled is an understatement – so thank you.
A special word of thanks also for Eric Siebert of vsphere-land.com for organizing all of this once more. No mean feat. Thank you Eric.
In this post I will now show you the steps involved in creating a Docker Swarm configuration using docker-machine with Photon Controller driver plugin. In previous posts, I showed how you can setup Photon OS to deploy Photon Controller and I also showed you how to build docker-machine for Photon Controller. Note that there are a lot of ways to deploy Swarm. Since I was given a demonstration on doing this using “Consul” for cluster membership and discovery, that is the mechanism that I am going to use here. Now, a couple of weeks back, we looked at deploying Docker Swarm using the “cluster” mechanism also available in Photon Controller. This mechanism used “etcd” for discovery, configuration, and so on. In this example, we are going to deploy Docker Swarm from the ground up, step-by-step, using the docker-machine with photon controller driver, but in this example we are going to use “Consul” which does something very similar to “etcd”.