Google Git
Sign in
fuchsia/third_party/github.com/moby/moby/b9e27acabc0551184c942e6ae190a2d0b74b02be
commit
b9e27acabc0551184c942e6ae190a2d0b74b02be
[log] [tgz]
author
Albin Kerouanton <albinker@gmail.com>
Thu Jan 04 11:25:37 2024 +0100
committer
Albin Kerouanton <albinker@gmail.com>
Thu Jan 04 11:50:04 2024 +0100
tree
cf58612226c32922de0d2f01172042468ceb66ad
parent
0a26cdf344d983eba7f2e1043beafaf750afd59a [diff]
libnet/d/bridge: dead code: no conflict on stale default nw

A check was added to the bridge driver to detect when it was called to
create the default bridge nw whereas a stale default bridge already
existed. In such case, the bridge driver was deleting the stale network
before re-creating it. This check was introduced in docker/libnetwork@6b158eac6a4877c27828f524ad1ca0ea4bd2a789
to fix an issue related to newly introduced live-restore.

However, since commit docker/docker@ecffb6d58cf89371e3f4a20f55c2e614dbdfe880,
the daemon doesn't even try to create default networks if there're
active sandboxes (ie. due to live-restore).

Thus, now it's impossible for the default bridge network to be stale and
to exists when the driver's CreateNetwork() method is called. As such,
the check introduced in the first commit mentioned above is dead code
and can be safely removed.

Signed-off-by: Albin Kerouanton <albinker@gmail.com>
1 file changed
tree: cf58612226c32922de0d2f01172042468ceb66ad
  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. oci/
  24. opts/
  25. pkg/
  26. plugin/
  27. profiles/
  28. project/
  29. quota/
  30. reference/
  31. registry/
  32. reports/
  33. restartmanager/
  34. runconfig/
  35. testutil/
  36. vendor/
  37. volume/
  38. .dockerignore
  39. .gitattributes
  40. .gitignore
  41. .golangci.yml
  42. .mailmap
  43. AUTHORS
  44. codecov.yml
  45. CONTRIBUTING.md
  46. docker-bake.hcl
  47. Dockerfile
  48. Dockerfile.simple
  49. Dockerfile.windows
  50. Jenkinsfile
  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.