M129: docker: fold the Go-module patches onto cos/release-R129

app-containers/docker is migrating to a 9999 live ebuild on M129. A live ebuild
builds the fork branch directly, so the Go-module patches that
docker-27.5.1-rN.ebuild applies from PATCHES=() can no longer be applied at
build time -- they have to live on the branch instead.

This commit folds all 5 of them in one go, applied in the ebuild's own
PATCHES=() order (not alphabetical order) so that every intermediate state
resolves cleanly:

  1. golang_org_x_crypto.patch
  2. golang_org_x_oauth2.patch
  3. golang_org_x_net.patch
  4. github_com_golang_jwt.patch
  5. fix-CVE-2026-33186-grpc.patch

Each patch is committed verbatim, exactly as COS applies it today. The squashed
tree is byte-identical to the previously uploaded 5-CL chain
(cos/201650-201654), which this CL replaces.

fix-CVE-2026-33186-grpc.patch bumps google.golang.org/grpc to the version that
carries the CVE-2026-33186 fix (b/541083274).

The 10 remaining entries in PATCHES=() are pure source changes and stay in
the ebuild.

Base is 4c9b3b011ae4, the current head of cos/release-R129.

BUG=b/535726916
TEST=tree-identity check against the base plus all 5 patches applied with GNU patch
RELEASE_NOTE=None

cos-patch: bug
Change-Id: I55f7c67aa8ec109e9653351d05008a8446bf039e
230 files changed
tree: 850ef9ec74aa8a0f74acc23c414382a2c51b66e6
  1. .devcontainer/
  2. .github/
  3. api/
  4. builder/
  5. cli/
  6. client/
  7. cmd/
  8. container/
  9. contrib/
  10. daemon/
  11. distribution/
  12. dockerversion/
  13. docs/
  14. errdefs/
  15. hack/
  16. image/
  17. integration/
  18. integration-cli/
  19. internal/
  20. layer/
  21. libcontainerd/
  22. libnetwork/
  23. man/
  24. oci/
  25. opts/
  26. pkg/
  27. plugin/
  28. profiles/
  29. project/
  30. quota/
  31. reference/
  32. registry/
  33. reports/
  34. restartmanager/
  35. runconfig/
  36. testutil/
  37. vendor/
  38. volume/
  39. .dockerignore
  40. .gitattributes
  41. .gitignore
  42. .golangci.yml
  43. .mailmap
  44. AUTHORS
  45. codecov.yml
  46. CONTRIBUTING.md
  47. docker-bake.hcl
  48. Dockerfile
  49. Dockerfile.simple
  50. Dockerfile.windows
  51. LICENSE
  52. MAINTAINERS
  53. Makefile
  54. NOTICE
  55. README.md
  56. ROADMAP.md
  57. SECURITY.md
  58. TESTING.md
  59. vendor.mod
  60. vendor.sum
  61. VENDORING.md
README.md

The Moby Project

Moby Project logo

Moby is an open-source project created by Docker to enable and accelerate software containerization.

It provides a “Lego set” of toolkit components, the framework for assembling them into custom container-based systems, and a place for all container enthusiasts and professionals to experiment and exchange ideas. Components include container build tools, a container registry, orchestration tools, a runtime and more, and these can be used as building blocks in conjunction with other tools and projects.

Principles

Moby is an open project guided by strong principles, aiming to be modular, flexible and without too strong an opinion on user experience. It is open to the community to help set its direction.

  • Modular: the project includes lots of components that have well-defined functions and APIs that work together.
  • Batteries included but swappable: Moby includes enough components to build fully featured container systems, but its modular architecture ensures that most of the components can be swapped by different implementations.
  • Usable security: Moby provides secure defaults without compromising usability.
  • Developer focused: The APIs are intended to be functional and useful to build powerful tools. They are not necessarily intended as end user tools but as components aimed at developers. Documentation and UX is aimed at developers not end users.

Audience

The Moby Project is intended for engineers, integrators and enthusiasts looking to modify, hack, fix, experiment, invent and build systems based on containers. It is not for people looking for a commercially supported system, but for people who want to work and learn with open source code.

Relationship with Docker

The components and tools in the Moby Project are initially the open source components that Docker and the community have built for the Docker Project. New projects can be added if they fit with the community goals. Docker is committed to using Moby as the upstream for the Docker Product. However, other projects are also encouraged to use Moby as an upstream, and to reuse the components in diverse ways, and all these uses will be treated in the same way. External maintainers and contributors are welcomed.

The Moby project is not intended as a location for support or feature requests for Docker products, but as a place for contributors to work on open source code, fix bugs, and make the code more useful. The releases are supported by the maintainers, community and users, on a best efforts basis only. For customers who want enterprise or commercial support, Docker Desktop and Mirantis Container Runtime are the appropriate products for these use cases.


Legal

Brought to you courtesy of our legal counsel. For more context, please see the NOTICE document in this repo.

Use and transfer of Moby may be subject to certain restrictions by the United States and other governments.

It is your responsibility to ensure that your use and/or transfer does not violate applicable laws.

For more information, please see https://www.bis.doc.gov

Licensing

Moby is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.