<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microvm on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/microvm/</link><description>Recent content in Microvm on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Jul 2026 15:50:13 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/microvm/index.xml" rel="self" type="application/rss+xml"/><item><title>Rivet reverse-engineers Docker Sandbox's undocumented microVM API</title><link>https://curadevops.metacog.co.kr/insights/2026-07-11-we-reverse-engineered-docker-sandbox-s-undocumented-microvm/</link><pubDate>Sat, 11 Jul 2026 15:50:13 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-11-we-reverse-engineered-docker-sandbox-s-undocumented-microvm/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Interesting look at microVM isolation internals beneath Docker Sandbox; no production operational change needed, but useful context for teams evaluating lightweight VM-based sandboxing for workloads.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Relevant background for teams considering Docker Sandbox as an isolated build or test environment; relies on an undocumented API so not actionable yet.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>