Google Git
Sign in
fuchsia / third_party / github.com / moby / moby / f2126bfc7fed97f0d692c6f796310e1c9f8dfa51
commitf2126bfc7fed97f0d692c6f796310e1c9f8dfa51[log] [tgz]
authorCory Snider <csnider@mirantis.com>Wed Jun 18 17:58:08 2025 -0400
committerCory Snider <csnider@mirantis.com>Wed Jun 18 19:20:40 2025 -0400
treeefeb7ca7a2cb952453316964b35df89efd9fc4b9
parent95aff4f75c6340dce6bcd50a80c0a9241d0d6180 [diff]
libnetwork: fix flaky Swarm service DNS

When libnetwork receives a watch event for a driver table entry from
NetworkDB it passes the event along to the interested driver. This code
contains a subtle bug: update events from NetworkDB are passed along to
the driver as Delete events! This bug was lying dormant as driver-table
entries can only be added by the driver, not updated. Now that NetworkDB
broadcasts an UpdateEvent to watchers if the entry is already known to
the local NetworkDB, irrespective of whether the event received from the
remote peer was a CREATE or UPDATE event, the bug is causing problems.
Whenever a remote node replaces an entry in the overlay_peer_table but
the intermediate delete state was not received by the local node, the
new CREATE event would be translated to an UpdateEvent by NetworkDB and
subsequently handled by the overlay driver as if the entry was deleted!

Bubble table UPDATE events up to the network driver as Update events.

Signed-off-by: Cory Snider <csnider@mirantis.com>
(cherry picked from commit a7f01d238ecf17a7bb849f0ae4d37f5021e0e4ef)
Signed-off-by: Cory Snider <csnider@mirantis.com>
1 file changed
tree: efeb7ca7a2cb952453316964b35df89efd9fc4b9
  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, and are not intended for customers who want enterprise or commercial support; Docker EE is the appropriate product 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.