Google Git
Sign in
fuchsia / third_party / github.com / moby / moby / 45876882585554409191c2f3b4089ec8cdee8ed0
commit45876882585554409191c2f3b4089ec8cdee8ed0[log] [tgz]
authorSebastiaan van Stijn <github@gone.nl>Tue Jun 25 18:39:31 2024 +0200
committerSebastiaan van Stijn <github@gone.nl>Wed Jun 26 14:05:47 2024 +0200
tree3fe8924616a4f77376d4e0ac829370bcbc859b84
parentff1e2c0de72a1bbbe4cdbe1558da57d327899df5 [diff]
api/types: deprecate ContainerJSONBase.Node, ContainerNode

The `Node` field and related `ContainerNode` type were used by the classic
(standalone) Swarm API. API documentation for this field was already removed
in 234d5a78fe383881ee952bf4c937eae3c54c7b51 (API 1.41 / docker 20.10), and
as the Docker Engine didn't implement these fields for the Swarm API, it
would always have been unset / nil.

Let's do a quick deprecation, and remove it on the next release.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit 1fc92361190bc77c44d76e68bd55018a29eb74d5)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
3 files changed
tree: 3fe8924616a4f77376d4e0ac829370bcbc859b84
  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.