You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: config-linux.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,7 +204,8 @@ The runtime MUST check that is possible to move the network interface to the con
204
204
The runtime MUST set the network device state to "up" after moving it to the network namespace to allow the container to send and receive network traffic through that device.
205
205
206
206
Notice that after deleting a network namespace, all its migratable network devices are moved to the default network namespace, virtual devices (veth, macvlan, ...) are destroyed.
207
-
The runtime MAY decide to move back or destroy the network device before the network namespace is deleted. If the network device is moved back, the runtime MUST set its state to "down" before moving it back to ensure that the interface is no longer active and won't interfere with other network operations or cause IP address conflicts.
207
+
The runtime MUST move back the network device before the network namespace is deleted.
208
+
The runtime MUST set the network device state to "down" before moving it back to ensure that the interface is no longer active and won't interfere with other network operations or cause IP address conflicts.
208
209
209
210
The name of the network device is the entry key.
210
211
Entry values are objects with the following properties:
@@ -213,7 +214,8 @@ Entry values are objects with the following properties:
213
214
The runtime MUST revert back the original name to guarantee the idempotence of operations, so a container that moves an interface and renames it can be created and destroyed multiple times with the same result.
214
215
***`addresses`***(array of strings, OPTIONAL)* - the IP addresses, IPv4 and or IPv6, of the device within the container in CIDR format (IP address / Prefix). All IPv4 addresses SHOULD be expressed in their decimal format, consisting of four decimal numbers separated by periods. Each number ranges from 0 to 255 and represents an octet of the address. IPv6 addresses SHOULD be represented in their canonical form as defined in RFC 5952.
215
216
The runtime MAY limit the number of addresses allowed.
216
-
The runtime MAY decide to revert back the original addreses.
217
+
The runtime MAY revert back the original addresses, keep the existing ones or completely
218
+
remove them, since the interface MUST be in down state can not present a problem.
217
219
***`hardwareAddress`***(string, OPTIONAL)* - represents the hardware address (e.g. MAC Address) of the device's network interface, represented as an IEEE 802 MAC-48, EUI-48, EUI-64, or a 20-octet IP over InfiniBand link-layer address.
218
220
The runtime MAY decide to revert back the original hardware address.
219
221
***`mtu`***(uint32, OPTIONAL)* - the MTU (Maximum Transmission Unit) size for the device.
0 commit comments