<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containerd on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/containerd/</link><description>Recent content in Containerd on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/containerd/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 1: Setting Up Your Apple Silicon Container Environment</title><link>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/setup-apple-silicon-container-env/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/setup-apple-silicon-container-env/</guid><description>&lt;p&gt;Developing containerized applications on Apple Silicon Macs presents a unique opportunity to leverage native ARM64 architecture for superior performance. While Docker Desktop has historically been the go-to, it often relies on Rosetta 2 emulation for x86-64 images or its own virtualization setup, which can introduce overhead. This chapter guides you through setting up a lean, high-performance local container environment that directly utilizes Apple&amp;rsquo;s native &lt;code&gt;Virtualization.framework&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;By the end of this chapter, you will have a fully functional Linux virtual machine running natively on your Apple Silicon Mac. This VM, managed by a tool that abstracts &lt;code&gt;Virtualization.framework&lt;/code&gt;, will host an OCI-compatible runtime like &lt;code&gt;containerd&lt;/code&gt;. You&amp;rsquo;ll then be able to use familiar &lt;code&gt;docker&lt;/code&gt; CLI commands to interact directly with this native ARM64 Linux environment, laying the groundwork for efficient local container development. This setup provides a robust, resource-friendly alternative, or complement, to traditional Docker Desktop installations.&lt;/p&gt;</description></item><item><title>Chapter 2: Creating and Configuring Your Linux Container Machine</title><link>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/create-linux-container-machine/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/create-linux-container-machine/</guid><description>&lt;p&gt;In the previous chapter, we prepared our macOS environment by installing essential developer tools. Now, it&amp;rsquo;s time to lay the foundation for our local container development: a lightweight Linux virtual machine (VM) running natively on your Apple Silicon Mac. This VM will serve as the host for all our containers, providing an ARM64 Linux environment that optimizes performance and ensures compatibility with modern container images.&lt;/p&gt;
&lt;p&gt;This chapter focuses on creating and configuring this core container machine. By the end, you&amp;rsquo;ll have a fully functional Linux VM, managed by &lt;code&gt;Colima&lt;/code&gt;, ready to receive and run OCI-compliant containers. This is a critical step, as it establishes the high-performance, native ARM64 execution environment that differentiates this approach from traditional x86-64 emulation or heavier Linux VMs.&lt;/p&gt;</description></item><item><title>Chapter 3: Efficient Project Volume Mounting with VirtioFS</title><link>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/efficient-volume-mounting-virtiofs/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/efficient-volume-mounting-virtiofs/</guid><description>&lt;p&gt;Local development often grinds to a halt when file I/O performance between your macOS host and a Linux virtual machine is subpar. This chapter directly addresses that bottleneck by guiding you through setting up high-performance file sharing using VirtioFS. This is crucial for containerized applications that frequently read and write to mounted project directories.&lt;/p&gt;
&lt;p&gt;By the end of this milestone, you will have a project directory on your macOS host seamlessly and performantly mounted inside your Linux container machine. This setup will be robust enough to handle demanding development tasks, such as installing dependencies with &lt;code&gt;npm install&lt;/code&gt; or &lt;code&gt;composer update&lt;/code&gt;, or performing frequent &lt;code&gt;git status&lt;/code&gt; checks on large codebases without frustrating delays. You&amp;rsquo;ll be fully prepared to build and run your application code directly from your local filesystem within the container environment.&lt;/p&gt;</description></item><item><title>Chapter 7: Authenticating and Pushing OCI Images to a Registry</title><link>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/push-oci-images-to-registry/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-silicon-local-containers-2026/push-oci-images-to-registry/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the previous chapters, you&amp;rsquo;ve established a robust local container development environment on your Apple Silicon Mac, built a Linux container machine using &lt;code&gt;Colima&lt;/code&gt;, efficiently mounted project volumes, and successfully built ARM64 OCI images for your sample application. Now, it&amp;rsquo;s time to share these images with the world, or at least with your team and deployment pipelines.&lt;/p&gt;
&lt;p&gt;This chapter focuses on the critical step of authenticating your local container environment with a remote OCI (Open Container Initiative) registry and pushing your custom-built images. Whether you&amp;rsquo;re deploying to a Kubernetes cluster, sharing with collaborators, or simply archiving your work, a container registry is the central hub for image management.&lt;/p&gt;</description></item></channel></rss>