<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>容器构建 on 黄文卓 | DevOps Engineer</title><link>https://socake.github.io/tags/%E5%AE%B9%E5%99%A8%E6%9E%84%E5%BB%BA/</link><description>Recent content in 容器构建 on 黄文卓 | DevOps Engineer</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor><webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster><copyright>© 2026 Wenzhuo Huang</copyright><lastBuildDate>Fri, 09 Jan 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/tags/%E5%AE%B9%E5%99%A8%E6%9E%84%E5%BB%BA/index.xml" rel="self" type="application/rss+xml"/><item><title>ko 实战：无 Dockerfile 构建 Go 容器镜像的正确姿势</title><link>https://socake.github.io/posts/ko-go-image-build/</link><pubDate>Fri, 09 Jan 2026 10:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/ko-go-image-build/</guid><description>同样是构建 Go 镜像，用 Dockerfile + BuildKit 要 2-3 分钟，用 ko 只需要 5-20 秒。差距来自 ko 不走 daemon、不写 tar、直接把 Go 编译产物塞进 OCI manifest。本文讲清楚这套 &amp;lsquo;Dockerfile-less&amp;rsquo; 构建到底怎么落地到生产，以及什么时候不该用它。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/ko-go-image-build/featured.jpg"/></item><item><title>BuildKit 缓存生产实战：从多阶段到远端 Registry Cache</title><link>https://socake.github.io/posts/buildkit-cache-production/</link><pubDate>Sat, 03 Jan 2026 10:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/buildkit-cache-production/</guid><description>BuildKit 的缓存体系看似简单一行 &amp;ndash;cache-to，实际生产里坑极多：mode=max 在多架构下的 manifest 行为、registry 后端每层 0.3s 的验证开销、cache mount 在 &amp;ndash;cache-to=registry 下不被导出的限制、GHA 后端 10GB 上限……本文基于真实 CI 流水线的调优记录，给出一套可复制的生产配置。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/buildkit-cache-production/featured.jpg"/></item></channel></rss>