<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Containers on Lonely Files on Scattered Drives</title>
    <link>/tags/containers/</link>
    <description>Recent content in Containers on Lonely Files on Scattered Drives</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Feb 2024 12:18:15 -0500</lastBuildDate><atom:link href="/tags/containers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Devs should not manually write Dockerfiles</title>
      <link>/posts/nomanualdockerfilecreation/</link>
      <pubDate>Thu, 08 Feb 2024 12:18:15 -0500</pubDate>
      
      <guid>/posts/nomanualdockerfilecreation/</guid>
      <description>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&amp;rsquo;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.</description>
    </item>
    
    <item>
      <title>CKA</title>
      <link>/posts/cka/</link>
      <pubDate>Tue, 27 Sep 2022 16:20:27 -0400</pubDate>
      
      <guid>/posts/cka/</guid>
      <description>I&amp;rsquo;ve passed my CKA!!! </description>
    </item>
    
    <item>
      <title>Migration to Hugo Part1</title>
      <link>/posts/migration-to-hugo-part1/</link>
      <pubDate>Sat, 30 Jan 2021 10:45:38 -0500</pubDate>
      
      <guid>/posts/migration-to-hugo-part1/</guid>
      <description>Well after thinking about migrating from Wordpress I&amp;rsquo;ve actually done it, I&amp;rsquo;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&amp;hellip; </description>
    </item>
    
    <item>
      <title>Kubernetes DNS issues</title>
      <link>/posts/kubernetes-dns-issues/</link>
      <pubDate>Thu, 21 Jan 2021 19:07:12 -0500</pubDate>
      
      <guid>/posts/kubernetes-dns-issues/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>CKAD Cert passed!!</title>
      <link>/posts/ckad-cert-passed/</link>
      <pubDate>Mon, 19 Oct 2020 20:30:00 -0400</pubDate>
      
      <guid>/posts/ckad-cert-passed/</guid>
      <description>I’ve passed my CKAD! this is a little delayed because I’ve been super busy. </description>
    </item>
    
    <item>
      <title>Site Outage</title>
      <link>/posts/site-outage/</link>
      <pubDate>Mon, 19 Oct 2020 20:30:00 -0400</pubDate>
      
      <guid>/posts/site-outage/</guid>
      <description>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. </description>
    </item>
    
    <item>
      <title>CoreDNS</title>
      <link>/posts/coredns/</link>
      <pubDate>Sat, 04 Jan 2020 23:57:01 -0500</pubDate>
      
      <guid>/posts/coredns/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>umds stack</title>
      <link>/posts/umds-stack/</link>
      <pubDate>Sun, 28 Apr 2019 14:30:13 -0400</pubDate>
      
      <guid>/posts/umds-stack/</guid>
      <description>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… </description>
    </item>
    
  </channel>
</rss>
