Another quick one. So I just learned about a new feature in Docker Desktop in which Docker Desktop can create a Dockerfile just by examining the code in your directory tree, which is pretty cool, so I updated my version of Docker Desktop to take advantage of this new feature, and it re-enforced my belief that Devs should not manually create Dockerfiles. Let’s have a look at the output from the command docker init # syntax=docker/dockerfile:1 # Comments are provided throughout this file to help you get started.

I’ve passed my CKA!!!

Well after thinking about migrating from Wordpress I’ve actually done it, I’ve migrated the blog over to Hugo a static site generator; I will have a full write up on the reasons behind me migrating off of Wordpress but for now I just wanted to write something quick and get the infra in place to make the move. More to come…

So I ran into an interesting issue today, I had provisioned a new k8s cluster using kubeADM but I replaced docker with containerD, everything was smooth and then I deployed prometheus and grafana using helm, and I noticed that I couldn’t connect grafana to prometheus I had installed istio so I thought that was the issue, maybe by default istio was messing with the pods network communication, but I also noticed that when I tried to install a dashboard from grafana I received an error, so the container couldn’t reach grafana.

I’ve passed my CKAD! this is a little delayed because I’ve been super busy.

It seems my mariadb container restarted which caused the site to become unstable, I killed both my front end pods and let k8s restart them and it all seems to be working right now, I need to do some investigation as to why the DB restarted.

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…