<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: kern</title>
    <description>The latest articles on DEV Community by kern (@kern-project).</description>
    <link>https://dev.to/kern-project</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4069813%2Fd0cc1e05-163a-4847-a986-4b57c032637c.png</url>
      <title>DEV Community: kern</title>
      <link>https://dev.to/kern-project</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kern-project"/>
    <language>en</language>
    <item>
      <title>I built kern – A CLI that replaces Docker with Unikernels (~10ms boot time, no daemon, pure QEMU)</title>
      <dc:creator>kern</dc:creator>
      <pubDate>Sun, 09 Aug 2026 11:49:07 +0000</pubDate>
      <link>https://dev.to/kern-project/i-built-kern-a-cli-that-replaces-docker-with-unikernels-10ms-boot-time-no-daemon-pure-qemu-5aa0</link>
      <guid>https://dev.to/kern-project/i-built-kern-a-cli-that-replaces-docker-with-unikernels-10ms-boot-time-no-daemon-pure-qemu-5aa0</guid>
      <description>&lt;p&gt;I've been building kern — a CLI that replaces Docker with unikernels.&lt;/p&gt;

&lt;p&gt;The idea is simple: instead of packaging your app in a container with a full Linux OS, kern compiles it into a single binary that contains exactly what your app needs and nothing else.&lt;/p&gt;

&lt;p&gt;The results are significant:&lt;br&gt;
→ ~10ms boot time (Docker: 800ms–2s)&lt;br&gt;
→ ~50 syscalls exposed (Docker: ~400)&lt;br&gt;
→ No Docker daemon. No kraft. Just QEMU.&lt;/p&gt;

&lt;p&gt;The build pipeline is entirely kraft-free:&lt;br&gt;
• skopeo downloads the Unikraft kernel from the OCI registry&lt;br&gt;
• buildah builds the rootfs without a Docker daemon&lt;br&gt;
• cpio packs the initramfs&lt;br&gt;
• objcopy fuses everything into a single .uki binary&lt;br&gt;
• ed25519 signs the image automatically&lt;br&gt;
• QEMU KVM runs it directly&lt;/p&gt;

&lt;p&gt;Every build is signed with ed25519 and generates an SBOM (SPDX-2.3) by default. No opt-in.&lt;/p&gt;

&lt;p&gt;Currently supports Node.js, Go, Rust and Python. Multi-service deployments work with kern compose, which sets up a real bridge network with DHCP between unikernels so services can talk to each other by name.&lt;/p&gt;

&lt;p&gt;There's also an official GitHub Action:&lt;br&gt;
uses: Kern-Unikernel/action@v1&lt;/p&gt;

&lt;p&gt;It's open source, MIT licensed, and still early — but already working in production on Linux with KVM.&lt;/p&gt;

&lt;p&gt;🔗 Website: &lt;a href="https://kern-vert.vercel.app" rel="noopener noreferrer"&gt;https://kern-vert.vercel.app&lt;/a&gt;&lt;br&gt;
🔗 GitHub: &lt;a href="https://github.com/Kern-Unikernel/Kern-Unikernel" rel="noopener noreferrer"&gt;https://github.com/Kern-Unikernel/Kern-Unikernel&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feedback welcome — especially from anyone who has dealt with container overhead in production.&lt;/p&gt;

&lt;h1&gt;
  
  
  opensource #devtools #unikernel #docker #linux #golang #rust #python #nodejs #qemu #security
&lt;/h1&gt;

</description>
      <category>cli</category>
      <category>devops</category>
      <category>docker</category>
      <category>softwaredevelopment</category>
    </item>
  </channel>
</rss>
