<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/containers/</link><description>Recent content in Containers 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/containers/index.xml" rel="self" type="application/rss+xml"/><item><title>WASM vs Docker: 35MB game engine binary vs hundreds-of-MB images</title><link>https://curadevops.metacog.co.kr/insights/2026-07-11-docker-images-are-hundreds-of-mb-a-full-game-engine-compiles/</link><pubDate>Sat, 11 Jul 2026 15:50:13 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-11-docker-images-are-hundreds-of-mb-a-full-game-engine-compiles/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Interesting size/portability comparison between WASM and container images, but no production infrastructure change warranted — worth tracking as WASM runtimes mature for platform workloads.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> WASM artifacts could eventually shrink build/publish times and registry storage costs, but no actionable pipeline change today — monitor for when toolchain support matures.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>