<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Docker on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/docker/</link>
    <description>Recent content in Docker on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 22 Sep 2016 22:26:52 -0700</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Application Container Fundamentals</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2016/container-fundamentals/</link>
      <pubDate>Thu, 22 Sep 2016 22:26:52 -0700</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2016/container-fundamentals/</guid>
      <description>At my current job, I spend a lot of time coaxing Docker to run containers while trying to avoid network failures, Docker bugs and kernel reference count issues. Recently, I&amp;rsquo;ve gotten into reading about how Docker and other containerization software is implemented under the hood. This is a write-up of my exploration and experiments looking at how container runtimes are implemented. Nothing in this essay is original, but I hope it helps some people.</description>
    </item>
  </channel>
</rss>
