So I had some challenges getting this up and running but I found a few blog post that helped me out: Setting up a vSphere lab with CoreDNS in Docker https://dev.to/robbmanes/running-coredns-as-a-dns-server-in-a-container-1d0 the first issue I had was a lot of Linux distros use systemd-resolved I am using photon OS and of course it does also so the first thing to do is sudo systemctl stop systemd-resolved sudo systemct disable systemd-resolved the reason for this is it consumes udp 53 which you’re container needs to run on the next issue I had was usually I can docker exec bash into a container, well this container is slim and I mean slim there is not bash no anything I kept getting an OCI error when I attempted to run any exec commands so I had to use the below docker command docker run -d -p 53:53/udp --rm --name coredns -v /static_content/coredns_config/:/root/ coredns/coredns -conf /root/Corefile again big help from the above blog postings.

I have created a umds stack file and have begun running umds on a single node docker swarm, also this version is using nginx as a web server instead of the simple http server python provides—the stack file can be found here Please stay tuned I will have a full write up on this soon…

So I have created a docker container for umds 6.7 please check it out on docker hub, I also have a complete write up as to how to use the container.

I just wanted to write a post on the differences between VMware’s Linux based UMDS 6.7 vs 6.5, one big change is that postgres is no longer required in 6.7. So here is a quick walkthrough in installing UMDS 6.7.x I will be using CentOS 7 minimal, mount your VCSA 6.7 DVD inside your cent VM and copy the VMware-UMDS-6.7.0-10164201.tar.gz from the umds directory to anywhere you desire /tmp is a good place.

So I wanted to enable Syslog on my PSC’s, VCSA’s, and on my Esxi servers and while enabling Syslog on the PSC’s and VCSA’s are pretty straight forward I did run into a bit of an issue enabling it on Esxi. The big gotcha is make certain the service is running, and that the firewall rule is enabled to allow UDP 514 or TCP 514 “Outbound” just like the pics below.

I’ve noticed a few issues on the site with the recent upgrade to 5.x—-Fixes coming soon.

So in my home lab I had to shutdown my server so I could add some memory and when I started everything back up I noticed that I few of my VM’s in my nested vSAN cluster had inaccessible next to them, so I started Googling around and I found the solution below: SSH into the vCenter that hosts your vSAN cluster(s) and then execute the below commands: rvc administrator@vsphere.local@localhost vsan.

So I had an issue trying to upgrade from ESXi 5.5 to 6.0, for some reason the upgrade process would not recognize the RAID 1 that ESXi was installed, after looking around I realized that the HP Smart Array firmware was on 3.x so I loaded the HP SPP which upgraded the firmware to 6.x, and viola, drive showed up during the upgrade process. Lesson here, keep your servers firmware up to date.

Ran into an issue today in which our gitlab server running in a docker container using VMware’s photonOS 1.x ran out of disk space on the /root partition by default this partition is only ~15GB; while the container was still running and I could log into gitlab I couldn’t clone any repos. The solution, simply add space to the disk in vCenter and boot the VM into GParted live an extend /dev/sda1 in my case, reboot, and all was good Thank goodness for GParted Live.

Well, I’ve built my first web app, it’s hosted on DigitalOcean, here it uses Bootstrap for the frontend with some skinning by MDB and the backend is SailsJS utilizing Mongo for a DB.