<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Docker on Wokron&#39;s Blog</title>
    <link>https://wokron.github.io/en/tags/docker/</link>
    <description>Recent content in Docker on Wokron&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>©2022-2026 Yitang Yang. All rights reserved.</copyright>
    <lastBuildDate>Mon, 13 Oct 2025 10:24:54 +0800</lastBuildDate>
    <atom:link href="https://wokron.github.io/en/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build a Container from Scratch with Namespaces</title>
      <link>https://wokron.github.io/en/posts/simple-container/</link>
      <pubDate>Mon, 13 Oct 2025 10:24:54 +0800</pubDate>
      <guid>https://wokron.github.io/en/posts/simple-container/</guid>
      <description>Container technology is built on three Linux kernel features: Namespaces, Cgroups, and Unionfs. They provide logical resource isolation, physical resource limits, and container filesystems, respectively.
Among these, Namespaces are the most critical. They implement isolation — the most essential aspect of virtualization. Even without Cgroups and with an alternative to Unionfs, you can still achieve much of what a container does, as long as you have Namespaces.
So in this article, we&amp;rsquo;ll try to build a simple container using Namespaces.</description>
    </item>
    <item>
      <title>Linux Users and Users in Containers</title>
      <link>https://wokron.github.io/en/posts/user-perm-and-container/</link>
      <pubDate>Sun, 12 Oct 2025 16:11:53 +0800</pubDate>
      <guid>https://wokron.github.io/en/posts/user-perm-and-container/</guid>
      <description>The era of multi-user operating systems is long over. People today generally don&amp;rsquo;t share computing resources by having multiple users log into the same OS — we have better virtualization technology for that.
But users still serve a purpose, the most important being permission isolation. There&amp;rsquo;s a lot to say on this topic, but we&amp;rsquo;ll focus on just the most critical points. Containers introduce additional quirks around users, which we&amp;rsquo;ll also discuss.</description>
    </item>
    <item>
      <title>Building TensorFlow from Source: Gotchas</title>
      <link>https://wokron.github.io/en/posts/build-tensorflow-from-source/</link>
      <pubDate>Mon, 20 Jan 2025 21:31:16 +0800</pubDate>
      <guid>https://wokron.github.io/en/posts/build-tensorflow-from-source/</guid>
      <description>A while back I found a small bug in TensorFlow. Now that I had some free time, I decided to submit a PR. The bug was fixed quickly, but when I tried to build TensorFlow locally, I ran into quite a few gotchas. Here are my notes.
1. So Many Versions, So Confusing Before we start building, let&amp;rsquo;s go over the relevant Nvidia GPU dependencies.
Nvidia has various GPU architectures. To distinguish between them, Nvidia uses Compute Capability.</description>
    </item>
  </channel>
</rss>
