One of the most notable changes in the vCenter Server Appliance (VCSA) in vSphere 6.5 is a switch of the underlying OS from SLES to VMware's very own Photon OS. With this change, VMware will now own the entire software stack within the VCSA (OS + Application). This will allow VMware to quickly respond and deliver OS and security updates to customers at a much quicker rate than it was possible before.
During my testing of the VCSA, I had a need to spin up a Docker Container. Given that the VCSA is now Photon OS based, this should be a pretty trivial thing to enable as it is with a standalone installation of Photon OS. After a bit of trial/error, I found what was needed to get this working on the VCSA. Before jumping into the solution, I should say that this is really for lab and educational purposes. In general, I would NOT recommend installing additional software on the VCSA, not only is this NOT supported by VMware but you may also potentially be impacting your vCenter Server by taking resources away from the main application. It is possible to constrain the amount of resources (CPU/Memory) allocated to the Docker Container, please refer to this resource for more information.
For smaller customers, the argument is that I can just run everything on a single system but in reality there are many benefits to having a separate management VM which can be Photon OS or any other OS that your organization supports. You can install additional management tools/scripts and you would not be artificially limited by the VCSA's environment which is really locked down to what is absolutely needed to run the vCenter Server application and its services.
Disclaimer: This is not officially supported by VMware, please use at your own risk.
Given that PowerCLI Core (Linux and Mac OS X) was just recently released, which also includes a Docker Container, I figure this would be a nice example to start with as I know a few of you have asked about this possibility 🙂
Step 1 - Install Docker by running the following command (you will need access to the internet either direct or proxy access from the VCSA)
tdnf -y install docker
Step 2 - Load the following kernel module which will allow us to start the Docker client by running the following command:
insmod /usr/lib/modules/$(uname -r)/kernel/net/bridge/bridge.ko
Note: The above command does not persist across reboots. If you would like to persist this configuration, please refer to the instructions at the very bottom.
Step 3 - Enable and start the Docker Client by running the following command:
systemctl enable docker
systemctl start docker
Step 4 - Pull down the PowerCLI Core Docker Image from Docker Hub by running the following command:
docker pull vmware/powerclicore
Step 5 - Start the PowerCLI Core Docker Container by running the following command:
docker run --rm -it --entrypoint='/usr/bin/powershell' vmware/powerclicore
As you can see from the screenshot above, you now have PowerShell and the PowerCLI module loaded running as a Docker Container on the VCSA 🙂 You can apply this to any Docker Container that you have created or pulling it directly from Docker Hub. If you prefer to build the PowerCLI Core Docker Container from the Dockerfile, you simply just need to download and extract the PowerCLI Core zip file onto the VCSA and then run the following command:
docker build -t vmware/powercli .
How to persist bridge module load across reboots:
Step 1 - Edit /etc/modprobe.d/modprobe.conf and remove the "install bridge /bin/false" entry.
Step 2 - Create a new file called /etc/modules-load.d/bridge.conf which contains the word "bridge" (no quotes). When the system boots up, it will iterate through all the module configuration file and load the respective modules. The bridge module is what is needed to start the Docker Daemon.
