1berry/docker-cli
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5718 from thaJeztah/remove_isolation_hint

Browse Source 
docs, man: remove confusing example for "--isolation"
This commit is contained in:
Sebastiaan van Stijn 2025-01-03 14:48:51 +01:00 committed by GitHub
commit 5be685e647
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/commandline/image_build.md
View File

@ -133,8 +133,6 @@ Linux namespaces. On Microsoft Windows, you can specify these values:
| `process` | Namespace isolation only. |
| `hyperv` | Hyper-V hypervisor partition-based isolation. |
Specifying the `--isolation` flag without a value is the same as setting `--isolation="default"`.
### <a name="security-opt"></a> Optional security options (--security-opt)
This flag is only supported on a daemon running on Windows, and only supports

2
man/docker-build.1.md
View File

@ -348,8 +348,6 @@ Linux namespaces. On Microsoft Windows, you can specify these values:
* `process`: Namespace isolation only.
* `hyperv`: Hyper-V hypervisor partition-based isolation.
Specifying the `--isolation` flag without a value is the same as setting `--isolation "default"`.
# HISTORY
March 2014, Originally compiled by William Henry (whenry at redhat dot com)
based on docker.com source material and internal work.

2
man/src/container/create-example.md
View File

@ -9,8 +9,6 @@ Linux namespaces. On Microsoft Windows, you can specify these values:
* `process`: Namespace isolation only.
* `hyperv`: Hyper-V hypervisor partition-based isolation.
Specifying the `--isolation` flag without a value is the same as setting `--isolation="default"`.
### Dealing with dynamically created devices (--device-cgroup-rule)
Devices available to a container are assigned at creation time. The