From 6f441382697e96313236d9aeb3754e68a525825b Mon Sep 17 00:00:00 2001 From: Cory Snider Date: Tue, 23 Jan 2024 18:26:45 -0500 Subject: [PATCH] libnetwork: fix tiny grammar mistake on design.md Co-authored-by: Farhim Ferdous <37705070+AluBhorta@users.noreply.github.com> Signed-off-by: Cory Snider --- libnetwork/docs/design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libnetwork/docs/design.md b/libnetwork/docs/design.md index 4967290bfc..07220313a8 100644 --- a/libnetwork/docs/design.md +++ b/libnetwork/docs/design.md @@ -52,7 +52,7 @@ Networks consist of *many* endpoints. `Endpoint` represents a Service Endpoint. It provides the connectivity for services exposed by a container in a network with other services provided by other containers in the network. `Network` object provides APIs to create and manage an endpoint. An endpoint can be attached to only one network. `Endpoint` creation calls are made to the corresponding `Driver` which is responsible for allocating resources for the corresponding `Sandbox`. Since `Endpoint` represents a Service and not necessarily a particular container, `Endpoint` has a global scope within a cluster. **Sandbox** -`Sandbox` object represents container's network configuration such as IP address, MAC address, routes, DNS entries. A `Sandbox` object is created when the user requests to create an endpoint on a network. The `Driver` that handles the `Network` is responsible for allocating the required network resources (such as the IP address) and passing the info called `SandboxInfo` back to libnetwork. libnetwork will make use of OS specific constructs (example: netns for Linux) to populate the network configuration into the containers that is represented by the `Sandbox`. A `Sandbox` can have multiple endpoints attached to different networks. Since `Sandbox` is associated with a particular container in a given host, it has a local scope that represents the Host that the Container belong to. +`Sandbox` object represents container's network configuration such as IP address, MAC address, routes, DNS entries. A `Sandbox` object is created when the user requests to create an endpoint on a network. The `Driver` that handles the `Network` is responsible for allocating the required network resources (such as the IP address) and passing the info called `SandboxInfo` back to libnetwork. libnetwork will make use of OS specific constructs (example: netns for Linux) to populate the network configuration into the containers that is represented by the `Sandbox`. A `Sandbox` can have multiple endpoints attached to different networks. Since `Sandbox` is associated with a particular container in a given host, it has a local scope that represents the Host that the Container belongs to. **CNM Attributes**