Google Git
Sign in
fuchsia/third_party/github.com/moby/moby/a379e026c91d6dce9828a5b6de0783f2c29404b8
commit
a379e026c91d6dce9828a5b6de0783f2c29404b8
[log] [tgz]
author
Albin Kerouanton <albinker@gmail.com>
Sat Aug 05 10:11:50 2023 +0200
committer
Cory Snider <csnider@mirantis.com>
Tue Mar 19 12:50:35 2024 -0400
tree
110b124866755f912c936a93e3571cc0aa144ada
parent
673020119f7b2da5dfa86685ef269a0aa8ba6033 [diff]
integration: Add a new networking integration test suite

This commit introduces a new integration test suite aimed at testing
networking features like inter-container communication, network
isolation, port mapping, etc... and how they interact with daemon-level
and network-level parameters.

So far, there's pretty much no tests making sure our networks are well
configured: 1. there're a few tests for port mapping, but they don't
cover all use cases ; 2. there're a few tests that check if a specific
iptables rule exist, but that doesn't prevent that specific iptables
rule to be wrong in the first place.

As we're planning to refactor how iptables rules are written, and change
some of them to fix known security issues, we need a way to test all
combinations of parameters. So far, this was done by hand, which is
particularly painful and time consuming. As such, this new test suite is
foundational to upcoming work.

Signed-off-by: Albin Kerouanton <albinker@gmail.com>
(cherry picked from commit 409ea700c7ea4d738287e2a471ad7b3d49b8590c)
Signed-off-by: Cory Snider <csnider@mirantis.com>
1 file changed
tree: 110b124866755f912c936a93e3571cc0aa144ada
  1. .github/
  2. api/
  3. builder/
  4. cli/
  5. client/
  6. cmd/
  7. container/
  8. contrib/
  9. daemon/
  10. distribution/
  11. dockerversion/
  12. docs/
  13. errdefs/
  14. hack/
  15. image/
  16. integration/
  17. integration-cli/
  18. internal/
  19. layer/
  20. libcontainerd/
  21. libnetwork/
  22. oci/
  23. opts/
  24. pkg/
  25. plugin/
  26. profiles/
  27. project/
  28. quota/
  29. reference/
  30. registry/
  31. reports/
  32. restartmanager/
  33. runconfig/
  34. testutil/
  35. vendor/
  36. volume/
  37. .dockerignore
  38. .gitattributes
  39. .gitignore
  40. .mailmap
  41. AUTHORS
  42. codecov.yml
  43. CONTRIBUTING.md
  44. docker-bake.hcl
  45. Dockerfile
  46. Dockerfile.e2e
  47. Dockerfile.simple
  48. Dockerfile.windows
  49. Jenkinsfile
  50. LICENSE
  51. MAINTAINERS
  52. Makefile
  53. NOTICE
  54. README.md
  55. ROADMAP.md
  56. SECURITY.md
  57. TESTING.md
  58. vendor.mod
  59. vendor.sum
  60. 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 system, 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.