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: content/en/docs/concepts/workloads/pods/_index.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -289,7 +289,11 @@ section.
289
289
290
290
## Privileged mode for containers
291
291
292
-
Any container in a pod can run in privileged mode to use operating system administrative capabilities
292
+
{{< note >}}
293
+
Your {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}} must support the concept of a privileged container for this setting to be relevant.
294
+
{{< /note >}}
295
+
296
+
Any container in a pod can run in priveleged mode to use operating system administrative capabilities
293
297
that would otherwise be inaccessible. This is available for both Windows and Linux.
294
298
295
299
### Linux containers
@@ -309,9 +313,6 @@ pods must run as Windows HostProcess containers. HostProcess pods run directly o
309
313
to perform administrative tasks as is done with Linux privileged containers. In order to use this feature, the
310
314
`WindowsHostProcessContainers`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) must be enabled.
311
315
312
-
{{< note >}}
313
-
Your {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}} must support the concept of a privileged container for this setting to be relevant.
0 commit comments