M117: docker: fold the Go-module patches onto cos/release-R117 app-containers/docker is migrating to a 9999 live ebuild on M117. A live ebuild builds the fork branch directly, so the Go-module patches that docker-24.0.9-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 8 of them in one go, applied in the ebuild's own PATCHES=() order (not alphabetical order) so that every intermediate state resolves cleanly: 1. docker-24.0.9-update-golang-grpc-version-go-mod.patch 2. docker-24.0.9-update-golang-grpc-version-related-code-changes.patch 3. docker-24.0.9-fix-CVE-2024-23653-buildkit-v0.12.5-upgrade.patch 4. docker-24.0.9-fix-CVE-2023-45288.patch 5. golang_org_x_crypto.patch 6. golang_org_x_oauth2.patch 7. golang_org_x_net.patch 8. github_com_golang_jwt.patch Each patch is committed verbatim, exactly as COS applies it today. The squashed tree is byte-identical to the previously uploaded 8-CL chain (cos/201547-201554), which this CL replaces. docker-24.0.9-fix-CVE-2024-23653-buildkit-v0.12.5-upgrade.patch is MIXED: it carries the buildkit v0.11.7 -> v0.12.5 vendored upgrade *and* one line of real source, `version.Version = "v0.12.5"` in builder/builder-next/worker/worker.go. moby's own vendor.mod says "when updating, also update the version in builder/builder-next/worker/worker.go", so the two halves cannot be separated; the whole patch is folded. One retained patch, docker-24.0.9-buildkit-v0.12.5-upgrade-related-changes.patch, imports github.com/moby/buildkit/executor/resources, which only exists after the fold. The overlays CL therefore must not merge before this one. The 12 remaining entries in PATCHES=() are pure source changes and stay in the ebuild. Base is fca702de7f71, the current head of cos/release-R117. BUG=b/535726916 TEST=tree-identity check against the base plus all 8 patches applied with GNU patch RELEASE_NOTE=None cos-patch: bug Change-Id: I56c5bc8161a5f807ae06885be8131c4ec660186d
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.
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.
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.
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, and are not intended for customers who want enterprise or commercial support; Docker EE is the appropriate product for these use cases.
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
Moby is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.