[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-docker-github-org-container-work-en":3,"article-related-docker-github-org-container-work-en":33,"series-industry-cf1e4743-3203-4145-97b5-41be640b5547":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},"cf1e4743-3203-4145-97b5-41be640b5547","docker-github-org-container-work-en","Docker’s GitHub org shows where container work happens","\u003Cp data-speakable=\"summary\">\u003Ca href=\"\u002Ftag\u002Fdocker\">Docker\u003C\u002Fa>’s \u003Ca href=\"\u002Ftag\u002Fgithub\">GitHub\u003C\u002Fa> org collects the project’s main tools, docs, and feedback channels in one place.\u003C\u002Fp>\u003Cp>Docker’s GitHub organization is more than a code dump: it points developers to the projects that shape image builds, multi-container apps, docs, and user feedback. The org lists 148 repositories, with pinned projects like \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fcompose\">compose\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuildx\">buildx\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuild-push-action\">build-push-action\u003C\u002Fa> giving a quick map of what matters most.\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Item\u003C\u002Fth>\u003Cth>Primary purpose\u003C\u002Fth>\u003Cth>Language\u003C\u002Fth>\u003Cth>Notable activity\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>compose\u003C\u002Ftd>\u003Ctd>Define and run multi-container apps\u003C\u002Ftd>\u003Ctd>Go\u003C\u002Ftd>\u003Ctd>37.5k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>buildx\u003C\u002Ftd>\u003Ctd>Extended build capabilities with BuildKit\u003C\u002Ftd>\u003Ctd>Go\u003C\u002Ftd>\u003Ctd>4.4k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>build-push-action\u003C\u002Ftd>\u003Ctd>Build and push images in GitHub Actions\u003C\u002Ftd>\u003Ctd>TypeScript\u003C\u002Ftd>\u003Ctd>5.3k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>docs\u003C\u002Ftd>\u003Ctd>Source for Docker documentation\u003C\u002Ftd>\u003Ctd>Markdown\u003C\u002Ftd>\u003Ctd>8.3k stars\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>desktop-feedback\u003C\u002Ftd>\u003Ctd>Feedback and feature requests for Docker Desktop\u003C\u002Ftd>\u003Ctd>Repository\u003C\u002Ftd>\u003Ctd>User reports\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>1. compose\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fcompose\">Docker Compose\u003C\u002Fa> is the clearest sign that Docker still centers real app workflows, not just container primitives. It lets teams define multi-container applications in one file and run them locally or in automation.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781101078934-w2yp.png\" alt=\"Docker’s GitHub org shows where container work happens\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>For developers who need a database, \u003Ca href=\"\u002Ftag\u002Fapi\">API\u003C\u002Fa>, and worker to start together, Compose is the project to inspect first. The repo is written in Go and is one of the largest pinned projects in the org, with 37.5k stars and 5.7k forks.\u003C\u002Fp>\u003Cul>\u003Cli>Use case: local dev stacks\u003C\u002Fli>\u003Cli>Use case: repeatable CI environments\u003C\u002Fli>\u003Cli>Language: Go\u003C\u002Fli>\u003Cli>Stars: 37.5k\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>2. buildx\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuildx\">Buildx\u003C\u002Fa> is the Docker CLI plugin for extended build capabilities with BuildKit. If you care about multi-platform images, advanced caching, or more control over image creation, this repo is the one to watch.\u003C\u002Fp>\u003Cp>It sits closer to the build pipeline than Compose does, and that makes it useful for teams shipping containers at scale. The repo shows 4.4k stars and 355 forks, which hints at steady adoption among build-heavy users.\u003C\u002Fp>\u003Ccode>docker buildx build --platform linux\u002Famd64,linux\u002Farm64 .\u003C\u002Fcode>\u003Ch2>3. build-push-action\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuild-push-action\">build-push-action\u003C\u002Fa> translates Docker builds into GitHub Actions workflows. It is the fastest route for teams that want to build and publish images from CI without writing a lot of shell glue.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781101078017-vjsv.png\" alt=\"Docker’s GitHub org shows where container work happens\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>The repository is \u003Ca href=\"\u002Ftag\u002Ftypescript\">TypeScript\u003C\u002Fa>-based and has 5.3k stars, which puts it in the same practical tier as Buildx for many teams. If your delivery pipeline already lives in GitHub, this action is often the most direct fit.\u003C\u002Fp>\u003Cul>\u003Cli>Best for: CI image builds\u003C\u002Fli>\u003Cli>Best for: registry publishing\u003C\u002Fli>\u003Cli>Works with: GitHub Actions\u003C\u002Fli>\u003Cli>Language: TypeScript\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>4. docs\u003C\u002Fh2>\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocs\">Docker’s documentation repo\u003C\u002Fa> is where product guidance becomes editable source. That matters because docs are often the first place users go when a build fails, a command changes, or a workflow needs confirmation.\u003C\u002Fp>\u003Cp>This repo is unusually active for a documentation project, with 8.3k stars and 93 forks. For teams trying to understand the current shape of Docker tooling, the docs repo is a better starting point than scattered blog posts.\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> is the most direct signal that the org wants user input in public. The repo is dedicated to feedback, ideas, and bug reports, which makes it useful for anyone trying to track pain points in the desktop product.\u003C\u002Fp>\u003Cp>The same feedback pattern also appears in \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fhub-feedback\">hub-feedback\u003C\u002Fa>, which covers Docker Hub. Together, these repos show that Docker keeps product issues close to the source instead of hiding them behind support forms.\u003C\u002Fp>\u003Cul>\u003Cli>Purpose: bug reports\u003C\u002Fli>\u003Cli>Purpose: feature requests\u003C\u002Fli>\u003Cli>Related repo: hub-feedback\u003C\u002Fli>\u003Cli>Audience: Desktop users\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How to decide\u003C\u002Fh2>\u003Cp>If you want to build and run applications, start with \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fcompose\">compose\u003C\u002Fa>. If your focus is CI image creation, \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuildx\">buildx\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fbuild-push-action\">build-push-action\u003C\u002Fa> are the pair to compare first.\u003C\u002Fp>\u003Cp>If you are trying to understand Docker itself, the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocs\">docs\u003C\u002Fa> repo and the feedback repos are the most useful entry points. They show both how Docker expects tools to be used and where users are still running into trouble.\u003C\u002Fp>","5 Docker repositories show where image builds, Compose apps, docs, and feedback live on GitHub.","github.com","https:\u002F\u002Fgithub.com\u002Fdocker",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781101078934-w2yp.png","industry","en","6b627ba3-9510-4e84-bf18-616097648ee8",[17,18,19,20,21,22,23,24],"Docker","GitHub","Docker Compose","Docker Buildx","Docker Desktop","GitHub Actions","container tools","open source",[26,27,28],"Compose is the best starting point for multi-container app work.","Buildx and build-push-action cover advanced builds and CI publishing.","Docs and feedback repos show how Docker handles user input and support.",0,"2026-06-10T14:17:22.825207+00:00","2026-06-10T14:17:22.807+00:00","d9924860-0489-4802-b2b9-7cfbd398cd09",{"tags":34,"relatedLang":45,"relatedPosts":49},[35,37,39,41,43],{"name":20,"slug":36},"docker-buildx",{"name":18,"slug":38},"github",{"name":21,"slug":40},"docker-desktop",{"name":19,"slug":42},"docker-compose",{"name":17,"slug":44},"docker",{"id":15,"slug":46,"title":47,"language":48},"docker-github-org-container-work-zh","5 個 Docker GitHub 倉庫看懂容器工作重心","zh",[50,56,62,68,74,80],{"id":51,"slug":52,"title":53,"cover_image":54,"image_url":54,"created_at":55,"category":13},"24ebb482-f6c2-405c-967e-61549b265310","manus-series-b-competitors-profile-en","Manus Raises Series B and Faces Box, Airtable","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781113677369-vi69.png","2026-06-10T17:47:29.876234+00:00",{"id":57,"slug":58,"title":59,"cover_image":60,"image_url":60,"created_at":61,"category":13},"016d4913-2f23-417d-b0a7-b45610852b8d","reid-hoffman-exit-microsoft-board-right-move-en","Reid Hoffman’s exit from Microsoft’s board is the right move","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781112768133-whcv.png","2026-06-10T17:32:20.518936+00:00",{"id":63,"slug":64,"title":65,"cover_image":66,"image_url":66,"created_at":67,"category":13},"5417136f-52b3-4b04-9c9b-5cbb4df36584","cuda-cores-memory-tensor-cores-win-en","CUDA cores matter, but memory and Tensor Cores win","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781110970740-rly0.png","2026-06-10T17:02:25.255458+00:00",{"id":69,"slug":70,"title":71,"cover_image":72,"image_url":72,"created_at":73,"category":13},"547493e6-e515-4aa3-bdcd-66eba6cf1fd5","codex-0-139-0-web-search-tooling-en","Codex 0.139.0 adds web search and cleaner tooling","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781104674116-naze.png","2026-06-10T15:17:22.112795+00:00",{"id":75,"slug":76,"title":77,"cover_image":78,"image_url":78,"created_at":79,"category":13},"be0d131f-9772-4b0e-8931-c9ede1d8ce55","cursor-mac-update-stuck-old-version-en","Cursor on Mac can get stuck on old versions","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781093876357-245p.png","2026-06-10T12:17:20.258974+00:00",{"id":81,"slug":82,"title":83,"cover_image":84,"image_url":84,"created_at":85,"category":13},"8b7626e4-c384-4703-b268-61e5626a4236","openai-ipo-wall-street-ai-test-en","OpenAI’s IPO will expose AI hype to Wall Street","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781067770153-r09j.png","2026-06-10T05:02:22.694946+00:00",[87,92,97,102,107,112,117,122,127,132],{"id":88,"slug":89,"title":90,"created_at":91},"d35a1bd9-e709-412e-a2df-392df1dc572a","ai-impact-2026-developments-market-en","AI's Impact in 2026: Key Developments and Market Shifts","2026-03-25T16:20:33.205823+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"5ed27921-5fd6-492e-8c59-78393bf37710","trumps-ai-legislative-framework-en","Trump's AI Legislative Framework: What's Inside?","2026-03-25T16:22:20.005325+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"e454a642-f03c-4794-b185-5f651aebbaca","nvidia-gtc-2026-key-highlights-innovations-en","NVIDIA GTC 2026: Key Highlights and Innovations","2026-03-25T16:22:47.882615+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"0ebb5b16-774a-4922-945d-5f2ce1df5a6d","claude-usage-diversifies-learning-curves-en","Claude Usage Diversifies, Learning Curves Emerge","2026-03-25T16:25:50.770376+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"69934e86-2fc5-4280-8223-7b917a48ace8","openclaw-ai-commoditization-concerns-en","OpenClaw's Rise Raises Concerns of AI Model Commoditization","2026-03-25T16:26:30.582047+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"b4b2575b-2ac8-46b2-b90e-ab1d7c060797","google-gemini-ai-rollout-2026-en","Google's Gemini AI Rollout Extended to 2026","2026-03-25T16:28:14.808842+00:00",{"id":118,"slug":119,"title":120,"created_at":121},"6e18bc65-42ae-4ad0-b564-67d7f66b979e","meta-llama4-fabricated-results-scandal-en","Meta's Llama 4 Scandal: Fabricated AI Test Results Unveiled","2026-03-25T16:29:15.482836+00:00",{"id":123,"slug":124,"title":125,"created_at":126},"bf888e9d-08be-4f47-996c-7b24b5ab3500","accenture-mistral-ai-deployment-en","Accenture and Mistral AI Team Up for AI Deployment","2026-03-25T16:31:01.894655+00:00",{"id":128,"slug":129,"title":130,"created_at":131},"5382b536-fad2-49c6-ac85-9eb2bae49f35","mistral-ai-high-stakes-2026-en","Mistral AI: Facing High Stakes in 2026","2026-03-25T16:31:39.941974+00:00",{"id":133,"slug":134,"title":135,"created_at":136},"9da3d2d6-b669-4971-ba1d-17fdb3548ed5","cursors-meteoric-rise-pressures-en","Cursor's Meteoric Rise Faces Industry Pressures","2026-03-25T16:32:21.899217+00:00"]