<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zig on SoloSoft</title><link>https://www.solosoft.dev/tags/zig/</link><description>Recent content in Zig on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/zig/index.xml" rel="self" type="application/rss+xml"/><item><title>Dockerc: Compile Docker Container Images into Standalone Portable Binaries</title><link>https://www.solosoft.dev/post/dockerc-container-binary-2026/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/dockerc-container-binary-2026/</guid><description>&lt;p&gt;Docker containers solved the &amp;ldquo;it works on my machine&amp;rdquo; problem, but they introduced a new one: &amp;ldquo;it works on my machine with Docker installed.&amp;rdquo; Containers require the Docker daemon, containerd, or at minimum a container runtime. For distributing command-line tools, desktop applications, or deployment artifacts, this dependency is a burden. &lt;strong&gt;Dockerc&lt;/strong&gt; takes a radically different approach &amp;ndash; it compiles entire Docker images into standalone binary executables.&lt;/p&gt;
&lt;p&gt;Written in Zig and available at &lt;a href="https://github.com/NilsIrl/dockerc"&gt;github.com/NilsIrl/dockerc&lt;/a&gt;, Dockerc reads a Docker image&amp;rsquo;s layers and produces a single, self-contained binary that embeds the filesystem, entry point, and runtime configuration. When executed, the binary unpacks itself into an in-memory filesystem (via tmpfs), sets up the process namespace, and runs the application. No Docker, no containerd, no root privileges required.&lt;/p&gt;</description></item></channel></rss>