[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-dockers-latest-releases-security-compose-zh":3,"article-related-dockers-latest-releases-security-compose-zh":34,"series-industry-d8c7a2ca-123e-49bf-a1c2-df856e63fce8":79},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":27,"views":31,"created_at":32,"published_at":33,"topic_cluster_id":11},"d8c7a2ca-123e-49bf-a1c2-df856e63fce8","dockers-latest-releases-security-compose-zh","Docker 這 5 版先看安全與 Compose","\u003Cp>最新 \u003Ca href=\"\u002Ftag\u002Fdocker\">Docker\u003C\u002Fa> 更新裡，先看哪 5 項才不會漏掉\u003Ca href=\"\u002Fnews\u002Fbitcoin-security-wake-up-call-zh\">安全風險\u003C\u002Fa>和部署變動？\u003C\u002Fp>\u003Cp data-speakable=\"summary\">這篇整理 5 個 Docker 近期重點更新，幫你判斷先升級安全修補、Compose 變更或 \u003Ca href=\"\u002Ftag\u002Fapi\">API\u003C\u002Fa> 擴充。\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>項目\u003C\u002Fth>\u003Cth>版本\u003C\u002Fth>\u003Cth>類型\u003C\u002Fth>\u003Cth>重點\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Docker Engine 29.7.2\u003C\u002Ftd>\u003Ctd>29.7.2\u003C\u002Ftd>\u003Ctd>Patch\u003C\u002Ftd>\u003Ctd>修正 panic、pull regression、網路問題\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Docker Compose v5.4.0\u003C\u002Ftd>\u003Ctd>5.4.0\u003C\u002Ftd>\u003Ctd>Patch\u003C\u002Ftd>\u003Ctd>資源重整模型更新\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Docker 29.7.0\u003C\u002Ftd>\u003Ctd>29.7.0\u003C\u002Ftd>\u003Ctd>Security\u003C\u002Ftd>\u003Ctd>內嵌 containerd，修補 CVE-2026-17106\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Docker Compose v5.3.0\u003C\u002Ftd>\u003Ctd>5.3.0\u003C\u002Ftd>\u003Ctd>Patch\u003C\u002Ftd>\u003Ctd>原生 init containers\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Docker 29.6.0 與 Moby API v1.55.0\u003C\u002Ftd>\u003Ctd>29.6.0 \u002F 1.55.0\u003C\u002Ftd>\u003Ctd>Feature\u003C\u002Ftd>\u003Ctd>attestation 讀取、資源更新 API\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>1. Docker Engine 29.7.2\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.docker.com\u002Fproducts\u002Fdocker-desktop\u002F\" target=\"_blank\" rel=\"noopener noreferrer\">Docker\u003C\u002Fa> 29.7.2 是這批更新裡最像「先救火」的版本。它修正了 \u003Ccode>docker service\u003C\u002Fcode> 指令的 panic、和絕對 hardlink 目標相關的 image pull regression，以及一些網路相容性問題。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786557772075-zir4.png\" alt=\"Docker 這 5 版先看安全與 Compose\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>如果你的叢集在最近升級後出現奇怪行為，這版值得先排。它的價值不在新功能，而在把常見操作拉回穩定狀態，讓服務\u003Ca href=\"\u002Fnews\u002Fsurgical-wam-video-pretraining-robot-control-zh\">控制\u003C\u002Fa>、拉鏡像和網路傳輸少出錯。\u003C\u002Fp>\u003Cul>\u003Cli>修正 service 指令 panic\u003C\u002Fli>\u003Cli>改善 image pull regression\u003C\u002Fli>\u003Cli>補上網路相容性問題\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>2. Docker Compose v5.4.0\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.docker.com\u002Fcompose\u002F\" target=\"_blank\" rel=\"noopener noreferrer\">Docker Compose\u003C\u002Fa> v5.4.0 把資源重整邏輯換成新的\u003Ca href=\"\u002Fnews\u002Fswe-bench-verified-model-leaderboard-limit-zh\">模型\u003C\u002Fa>，重點放在 volumes 與 networks 的一致性。對多容器應用來說，這會影響 declared state 和實際狀態如何對齊。\u003C\u002Fp>\u003Cp>它也修掉一些細節問題，例如 zero-replica services 的 hashing，以及 service selection 被忽略時的警告。若你的團隊把 Compose 當成基礎設施程式碼，這版會讓狀態管理更可預測。\u003C\u002Fp>\u003Cul>\u003Cli>新的資源重整模型\u003C\u002Fli>\u003Cli>更穩定的 volumes 與 networks 處理\u003C\u002Fli>\u003Cli>修正 zero-replica hashing 行為\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>3. Docker 29.7.0\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.docker.com\u002Fproducts\u002Fdocker-desktop\u002F\" target=\"_blank\" rel=\"noopener noreferrer\">Docker\u003C\u002Fa> 29.7.0 是這波裡最受安全團隊關注的版本。它加入實驗性的 embedded containerd，讓某些環境的管理流程可能更簡化，但因為仍屬 experimental，正式導入前最好先做測試。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786557782316-lneo.png\" alt=\"Docker 這 5 版先看安全與 Compose\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>更重要的是，它修補了 CVE-2026-17106，並帶來網路可靠性修正，以及 Go 和 runc 的依賴更新。若你要先挑一版處理風險，這版通常會排在前面。\u003C\u002Fp>\u003Cul>\u003Cli>實驗性 embedded containerd\u003C\u002Fli>\u003Cli>修補 CVE-2026-17106\u003C\u002Fli>\u003Cli>更新 Go 與 runc 依賴\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>4. Docker Compose v5.3.0\u003C\u002Fh2>\u003Cp>Docker Compose v5.3.0 加入原生 init containers，適合那些需要在主服務啟動前先做初始化工作的場景。像是資料庫 migration、設定檔準備，或任何有明確前置步驟的服務，都會更好表達。\u003C\u002Fp>\u003Cp>這版也包含修正與內部遷移，方向很明確：讓 Compose 能直接描述更多生命週期步驟，減少額外腳本或 wrapper tooling 的依賴。\u003C\u002Fp>\u003Cul>\u003Cli>原生 init containers\u003C\u002Fli>\u003Cli>更清楚的啟動順序\u003C\u002Fli>\u003Cli>適合先初始化再啟動的工作流\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>5. Docker 29.6.0 與 Moby API v1.55.0\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmoby\u002Fmoby\" target=\"_blank\" rel=\"noopener noreferrer\">Moby\u003C\u002Fa> API v1.55.0 和 Docker 29.6.0 把重點放在平台自動化。API 新增 image attestation 擷取能力，工具可以直接從 daemon 讀取 in-toto provenance 與 SPDX SBOM 資料。\u003C\u002Fp>\u003Cp>同一條版本線還加入 container resource update endpoint，並改善 image pruning、push 行為與 rootless networking。對內部建置系統或政策檢查來說，這些更新讓 metadata 存取與資源控制更容易串接。\u003C\u002Fp>\u003Cul>\u003Cli>新增 image attestation 讀取\u003C\u002Fli>\u003Cli>提供 container resource update API\u003C\u002Fli>\u003Cli>更適合 SBOM 與 provenance 自動化\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>怎麼挑\u003C\u002Fh2>\u003Cp>如果你現在最在意的是穩定性，先看 Docker Engine 29.7.2；如果要處理安全風險，29.7.0 應該排最前。Compose 使用者則可把 v5.4.0 當成資源管理的優先升級，v5.3.0 則適合需要 init containers 的團隊。\u003C\u002Fp>\u003Cp>平台與資安團隊會更在意 Docker 29.6.0 和 Moby API v1.55.0，因為它們直接影響 attestation、SBOM 和資源更新的自動化。簡單說，先升 patch 版保穩定，再看 Compose 版調整流程，最後才把 API 新能力納入管線。\u003C\u002Fp>","13 版 Docker 更新裡，先看 5 個重點：安全修補、Compose 重整模型、API 擴充與穩定性修正。","releasebytes.com","https:\u002F\u002Freleasebytes.com\u002Fdocker",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786557772075-zir4.png","industry","zh","bb70741d-b446-4f24-8828-94d571538e3b",[17,18,19,20,21,22,23,24,25,26],"Docker","Docker Engine","Docker Compose","Moby API","security fixes","CVE-2026-17106","containerd","SBOM","provenance","API updates",[28,29,30],"29.7.2 先處理 panic、pull regression 和網路問題，適合先救火。","29.7.0 把安全修補和 experimental embedded containerd 放在同一版，值得優先評估。","Compose 的 5.4.0 與 5.3.0 分別偏向資源重整與 init containers，適合不同工作流。",1,"2026-08-12T18:02:27.019175+00:00","2026-08-12T18:02:27.016+00:00",{"tags":35,"relatedLang":38,"relatedPosts":42},[36],{"name":17,"slug":37},"docker",{"id":15,"slug":39,"title":40,"language":41},"dockers-latest-releases-security-compose-en","Docker’s latest releases now center security and Compose","en",[43,49,55,61,67,73],{"id":44,"slug":45,"title":46,"cover_image":47,"image_url":47,"created_at":48,"category":13},"e0d0476a-e3d5-4bf7-995b-e5416f5e392a","moka-ai-hrms-three-layer-architecture-zh","Moka AI 不是锦上添花，HRMS 选型正在转向三层架构","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786611776096-cy66.png","2026-08-13T09:02:28.103219+00:00",{"id":50,"slug":51,"title":52,"cover_image":53,"image_url":53,"created_at":54,"category":13},"3640e980-0be1-408e-b5fe-a1ad42022b61","ai-hardware-rally-short-sellers-august-2026-zh","AI硬件反攻，8月空頭更難做","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786584781842-0bny.png","2026-08-13T01:32:36.671063+00:00",{"id":56,"slug":57,"title":58,"cover_image":59,"image_url":59,"created_at":60,"category":13},"f1349fae-7cbd-49a0-9d6a-ceaa65b51c1e","pixel-11-launch-live-google-reveals-zh","Pixel 11 發表會重點整理","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786581163428-ivyj.png","2026-08-13T00:32:20.178966+00:00",{"id":62,"slug":63,"title":64,"cover_image":65,"image_url":65,"created_at":66,"category":13},"07408fa7-809f-49e2-873d-427cb10c0c15","claude-invisible-watermark-right-direction-zh","Claude隱形水印是正確方向，不是暴政","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786579370713-ic6h.png","2026-08-13T00:02:25.128006+00:00",{"id":68,"slug":69,"title":70,"cover_image":71,"image_url":71,"created_at":72,"category":13},"3c2ec309-2f90-4d47-89e0-3fbe4070e3d1","bitcoin-security-wake-up-call-zh","8 則更新暴露比特幣安全風險","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786519984408-scff.png","2026-08-12T07:32:37.017044+00:00",{"id":74,"slug":75,"title":76,"cover_image":77,"image_url":77,"created_at":78,"category":13},"34245559-af66-4e72-9702-503c686f18f5","fpt-openai-select-status-channel-play-not-moat-zh","FPT 的 OpenAI Select 身分是通路優勢，不是護城河","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786494761936-sx11.png","2026-08-12T00:32:19.178576+00:00",[80,85,90,95,100,105,110,115,120,125],{"id":81,"slug":82,"title":83,"created_at":84},"ee073da7-28b3-4752-a319-5a501459fb87","ai-in-2026-what-actually-matters-now-zh","2026 AI 真正重要的事","2026-03-26T07:09:12.008134+00:00",{"id":86,"slug":87,"title":88,"created_at":89},"83bd1795-8548-44c9-9a7e-de50a0923f71","trump-ai-framework-power-speech-state-preemption-zh","川普 AI 框架瞄準電力、言論與州權","2026-03-26T07:12:18.695466+00:00",{"id":91,"slug":92,"title":93,"created_at":94},"ea6be18b-c903-4e54-97b7-5f7447a612e0","nvidia-gtc-2026-big-ai-announcements-zh","NVIDIA GTC 2026 重點拆解","2026-03-26T07:14:26.62638+00:00",{"id":96,"slug":97,"title":98,"created_at":99},"4bcec76f-4c36-4daa-909f-54cd702f7c93","claude-users-spreading-out-and-getting-better-zh","Claude 用戶更分散，也更會用","2026-03-26T07:22:52.325888+00:00",{"id":101,"slug":102,"title":103,"created_at":104},"bd903b15-2473-4178-9789-b7557816e535","openclaw-raises-hard-question-for-ai-models-zh","OpenClaw 逼問 AI 模型價值","2026-03-26T07:24:54.707486+00:00",{"id":106,"slug":107,"title":108,"created_at":109},"eeac6b9e-ad9d-4831-8eec-8bba3f9bca6a","gap-google-gemini-checkout-fashion-search-zh","Gap 把結帳搬進 Gemini","2026-03-26T07:28:23.937768+00:00",{"id":111,"slug":112,"title":113,"created_at":114},"0740e53f-605d-4d57-8601-c10beb126f3c","google-pushes-gemini-transition-to-march-2026-zh","Google 把 Gemini 轉換延到 2026 年 3…","2026-03-26T07:30:12.825269+00:00",{"id":116,"slug":117,"title":118,"created_at":119},"e660d801-2421-4529-8fa9-86b82b066990","metas-llama-4-benchmark-scandal-gets-worse-zh","Meta Llama 4 分數風波又擴大","2026-03-26T07:34:21.156421+00:00",{"id":121,"slug":122,"title":123,"created_at":124},"183f9e7c-e143-40bb-a6d5-67ba84a3a8bc","accenture-mistral-ai-sovereign-enterprise-deal-zh","Accenture 攜手 Mistral AI 賣主權 AI","2026-03-26T07:38:14.818906+00:00",{"id":126,"slug":127,"title":128,"created_at":129},"191d9b1b-768a-478c-978c-dd7431a38149","mistral-ai-faces-its-hardest-year-yet-zh","Mistral AI 迎來最硬的一年","2026-03-26T07:40:23.716374+00:00"]