[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-docker-github-org-container-work-zh":3,"article-related-docker-github-org-container-work-zh":33,"series-industry-6b627ba3-9510-4e84-bf18-616097648ee8":86},{"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":25,"views":29,"created_at":30,"published_at":31,"topic_cluster_id":32},"6b627ba3-9510-4e84-bf18-616097648ee8","docker-github-org-container-work-zh","5 個 Docker GitHub 倉庫看懂容器工作重心","\u003Cp data-speakable=\"summary\">這份清單整理 \u003Ca href=\"\u002Ftag\u002Fdocker\">Docker\u003C\u002Fa> \u003Ca href=\"\u002Ftag\u002Fgithub\">GitHub\u003C\u002Fa> 組織裡最值得先看的 5 個倉庫，幫你判斷該從建置、Compose、文件還是回饋入口開始。\u003C\u002Fp>\u003Cp>Docker 的 GitHub 組織不是單純的程式碼倉庫集合，而是一張工作地圖。看完這 5 個項目，你大致就能判斷：哪些專案管多容器應用、哪些專案管影像建置、哪些地方能追文件\u003Ca href=\"\u002Fnews\u002Fupdate-cursor-in-1-minute-zh\">更新\u003C\u002Fa>，還有哪些入口直接收使用者回饋。整個 org 一共有 148 個倉庫，先看釘選專案最省時間。\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>項目\u003C\u002Fth>\u003Cth>主要用途\u003C\u002Fth>\u003Cth>語言／形式\u003C\u002Fth>\u003Cth>可觀察指標\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>compose\u003C\u002Ftd>\u003Ctd>定義與執行多容器應用\u003C\u002Ftd>\u003Ctd>Go\u003C\u002Ftd>\u003Ctd>37.5k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>buildx\u003C\u002Ftd>\u003Ctd>擴充 BuildKit 建置能力\u003C\u002Ftd>\u003Ctd>Go\u003C\u002Ftd>\u003Ctd>4.4k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>build-push-action\u003C\u002Ftd>\u003Ctd>在 GitHub Actions 建置並推送映像\u003C\u002Ftd>\u003Ctd>TypeScript\u003C\u002Ftd>\u003Ctd>5.3k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>docs\u003C\u002Ftd>\u003Ctd>Docker 文件來源\u003C\u002Ftd>\u003Ctd>Markdown\u003C\u002Ftd>\u003Ctd>8.3k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>desktop-feedback\u003C\u002Ftd>\u003Ctd>Docker Desktop 回饋與問題追蹤\u003C\u002Ftd>\u003Ctd>回饋倉庫\u003C\u002Ftd>\u003Ctd>公開 issue\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>1. compose：先看它，就知道 Docker 還在管應用流程\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fcompose\">Docker Compose\u003C\u002Fa> 是最能代表 Docker 實際使用場景的專案。它不是只處理容器本身，而是讓你用一份設定把 \u003Ca href=\"\u002Ftag\u002Fapi\">API\u003C\u002Fa>、資料庫、worker 一起拉起來。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781101082779-iaoi.png\" alt=\"5 個 Docker GitHub 倉庫看懂容器工作重心\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>如果你的團隊在意本機開發環境、測試環境一致性，或 CI 裡需要可重現的多服務啟動流程，Compose 幾乎一定會排在第一順位。它是 Go 專案，也是釘選倉庫中最醒目的核心之一。\u003C\u002Fp>\u003Cul>\u003Cli>適合：本機開發堆疊\u003C\u002Fli>\u003Cli>適合：可重現的 CI 環境\u003C\u002Fli>\u003Cli>語言：Go\u003C\u002Fli>\u003Cli>參考：37.5k stars\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>2. buildx：想看進階建置，從這裡切入\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuildx\">Buildx\u003C\u002Fa> 是 Docker CLI 的延伸工具，重點在更強的建置能力，背後搭配 BuildKit 使用。若你關心多平台映像、快取策略，或想把建置流程做得更細，這個倉庫比一般教學更有參考價值。\u003C\u002Fp>\u003Cp>它比 Compose 更貼近映像生成流程，也更接近實際交付管線。對需要同時支援 amd64 與 arm64 的團隊來說，Buildx 常常是最先要理解的工具。\u003C\u002Fp>\u003Ccode>docker buildx build --platform linux\u002Famd64,linux\u002Farm64 .\u003C\u002Fcode>\u003Ch2>3. build-push-action：GitHub Actions 裡最直接的出貨路徑\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuild-push-action\">build-push-action\u003C\u002Fa> 把 Docker 建置流程包進 GitHub Actions，\u003Ca href=\"\u002Fnews\u002Fsightengine-visual-moderation-right-choice-zh\">適合\u003C\u002Fa>想在 CI 裡直接建置並推送映像的團隊。它的價值不在命令有多新，而在於少寫很多 shell glue。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781101075731-1jdz.png\" alt=\"5 個 Docker GitHub 倉庫看懂容器工作重心\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>如果你的部署與版本控管都已經在 GitHub 上，這個 action 往往比自己拼腳本更穩。它是 \u003Ca href=\"\u002Ftag\u002Ftypescript\">TypeScript\u003C\u002Fa> 專案，和 Buildx 一起看，最容易看出 Docker 官方對自動化交付的思路。\u003C\u002Fp>\u003Cul>\u003Cli>適合：CI 映像建置\u003C\u002Fli>\u003Cli>適合：推送到 registry\u003C\u002Fli>\u003Cli>整合：GitHub Actions\u003C\u002Fli>\u003Cli>語言：TypeScript\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>4. docs：文件倉庫比部落格更接近真實狀態\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocs\">Docker 文件倉庫\u003C\u002Fa> 是產品說明的源頭。對使用者來說，文件常常比原始碼更早暴露變動：命令改了、流程調整了、某個\u003Ca href=\"\u002Fnews\u002Fsix-ai-features-short-video-apps-need-2026-zh\">功能\u003C\u002Fa>行為變了，這裡通常最先反映。\u003C\u002Fp>\u003Cp>對想掌握 Docker 現況的人，docs 比零散文章更值得追。它不只是教學頁面，而是產品定義的一部分，從更新節奏也能看出 Docker 在哪些區域持續投入。\u003C\u002Fp>\u003Ccode>docs.docker.com\u003C\u002Fcode>\u003Ch2>5. desktop-feedback：想看使用者痛點，這裡最直接\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdesktop-feedback\">Docker Desktop feedback\u003C\u002Fa> 把問題回報、功能建議與使用者抱怨放到公開倉庫裡。這代表 Docker 願意讓產品摩擦點直接曝光，而不是只留在客服表單裡。\u003C\u002Fp>\u003Cp>同樣的模式也出現在 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fhub-feedback\">hub-feedback\u003C\u002Fa>。如果你想知道桌面端或 Hub 哪些地方最常出問題，這些 feedback 倉庫通常比公告更有資訊量。\u003C\u002Fp>\u003Cul>\u003Cli>用途：bug reports\u003C\u002Fli>\u003Cli>用途：feature requests\u003C\u002Fli>\u003Cli>相關：hub-feedback\u003C\u002Fli>\u003Cli>對象：Desktop 使用者\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>怎麼挑：先看工作流，再看產品訊號\u003C\u002Fh2>\u003Cp>如果你要的是「怎麼把應用跑起來」，先看 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fcompose\">compose\u003C\u002Fa>。如果你在意的是映像如何被建置、最佳化與自動化，\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuildx\">buildx\u003C\u002Fa> 和 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuild-push-action\">build-push-action\u003C\u002Fa> 應該一起比較。\u003C\u002Fp>\u003Cp>如果你想理解 Docker 產品本身的變化，\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocs\">docs\u003C\u002Fa> 和各種 feedback 倉庫更有價值。它們不只告訴你工具怎麼用，也會透露使用者卡在哪裡、官方又把重心放在哪裡。\u003C\u002Fp>","5 個 Docker 倉庫就能看出容器建置、Compose、文件與回饋在哪裡運作，也能判斷先看哪個專案。","github.com","https:\u002F\u002Fgithub.com\u002Fdocker",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781101082779-iaoi.png","industry","zh","cf1e4743-3203-4145-97b5-41be640b5547",[17,18,19,20,21,22,23,24],"Docker","GitHub","Compose","Buildx","Docker Desktop","CI\u002FCD","容器","文件",[26,27,28],"Compose 最適合看多容器應用與本機開發流程。","Buildx 與 build-push-action 最能看出 Docker 的建置與 CI 自動化。","docs 與 feedback 倉庫能反映產品說明和使用者痛點。",2,"2026-06-10T14:17:22.359514+00:00","2026-06-10T14:17:22.351+00:00","fe20f6f6-432b-47bf-a410-a5f516d885ed",{"tags":34,"relatedLang":45,"relatedPosts":49},[35,37,39,41,43],{"name":18,"slug":36},"github",{"name":21,"slug":38},"docker-desktop",{"name":19,"slug":40},"compose",{"name":20,"slug":42},"buildx",{"name":17,"slug":44},"docker",{"id":15,"slug":46,"title":47,"language":48},"docker-github-org-container-work-en","Docker’s GitHub org shows where container work happens","en",[50,56,62,68,74,80],{"id":51,"slug":52,"title":53,"cover_image":54,"image_url":54,"created_at":55,"category":13},"b389653a-3d79-447c-92c3-dd3046ade459","manus-series-b-competitors-profile-zh","Manus 募資後正面對 Box、Airtable","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781113676523-ec9h.png","2026-06-10T17:47:29.385169+00:00",{"id":57,"slug":58,"title":59,"cover_image":60,"image_url":60,"created_at":61,"category":13},"c6712c6a-0d6a-43e0-a8d0-52a936f0c858","reid-hoffman-exit-microsoft-board-right-move-zh","Reid Hoffman 離開 Microsoft 董事會是對的","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781112768945-5q4d.png","2026-06-10T17:32:20.021427+00:00",{"id":63,"slug":64,"title":65,"cover_image":66,"image_url":66,"created_at":67,"category":13},"15c682f7-7da1-4ecc-abb8-adec3192f9e4","cuda-cores-memory-tensor-cores-win-zh","CUDA 核心重要，但記憶體與 Tensor Core 才決定訓練速度","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781110977227-kfgw.png","2026-06-10T17:02:24.803101+00:00",{"id":69,"slug":70,"title":71,"cover_image":72,"image_url":72,"created_at":73,"category":13},"e6150343-1fa8-4cb1-aeda-ac3014747680","codex-0-139-0-web-search-tooling-zh","Codex 0.139.0 把搜尋與工具整合補齊了","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781104674394-of0a.png","2026-06-10T15:17:21.664159+00:00",{"id":75,"slug":76,"title":77,"cover_image":78,"image_url":78,"created_at":79,"category":13},"b47005a4-25f4-4e88-b63e-f2d45f67a06d","cursor-mac-update-stuck-old-version-zh","Cursor 在 Mac 卡住舊版時，先做這 5 件事","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781093865955-o89c.png","2026-06-10T12:17:19.671432+00:00",{"id":81,"slug":82,"title":83,"cover_image":84,"image_url":84,"created_at":85,"category":13},"e95cd367-6b7c-42a0-b9d3-7c0adac6a1d1","openai-ipo-wall-street-ai-test-zh","OpenAI 上市將把 AI 熱潮交給華爾街驗證","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781067772704-97ll.png","2026-06-10T05:02:22.294241+00:00",[87,92,97,102,107,112,117,122,127,132],{"id":88,"slug":89,"title":90,"created_at":91},"ee073da7-28b3-4752-a319-5a501459fb87","ai-in-2026-what-actually-matters-now-zh","2026 AI 真正重要的事","2026-03-26T07:09:12.008134+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"83bd1795-8548-44c9-9a7e-de50a0923f71","trump-ai-framework-power-speech-state-preemption-zh","川普 AI 框架瞄準電力、言論與州權","2026-03-26T07:12:18.695466+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"ea6be18b-c903-4e54-97b7-5f7447a612e0","nvidia-gtc-2026-big-ai-announcements-zh","NVIDIA GTC 2026 重點拆解","2026-03-26T07:14:26.62638+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"4bcec76f-4c36-4daa-909f-54cd702f7c93","claude-users-spreading-out-and-getting-better-zh","Claude 用戶更分散，也更會用","2026-03-26T07:22:52.325888+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"bd903b15-2473-4178-9789-b7557816e535","openclaw-raises-hard-question-for-ai-models-zh","OpenClaw 逼問 AI 模型價值","2026-03-26T07:24:54.707486+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"eeac6b9e-ad9d-4831-8eec-8bba3f9bca6a","gap-google-gemini-checkout-fashion-search-zh","Gap 把結帳搬進 Gemini","2026-03-26T07:28:23.937768+00:00",{"id":118,"slug":119,"title":120,"created_at":121},"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":123,"slug":124,"title":125,"created_at":126},"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":128,"slug":129,"title":130,"created_at":131},"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":133,"slug":134,"title":135,"created_at":136},"191d9b1b-768a-478c-978c-dd7431a38149","mistral-ai-faces-its-hardest-year-yet-zh","Mistral AI 迎來最硬的一年","2026-03-26T07:40:23.716374+00:00"]