Improvements to Enhanced Container Isolation (ECI) limitations section .. (#20541)

* eci: mention KinD alternative.

Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>

* eci: indicate it's not supported with Windows native containers.

Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>

* eci: a few typo fixes in the ECI limitations section.

Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>

---------

Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>
This commit is contained in:
Cesar Talledo 2024-08-06 00:44:05 -07:00 committed by GitHub
parent 2c51a10815
commit 133f7aa54b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 16 additions and 2 deletions

View File

@ -82,8 +82,15 @@ these won't work properly.
### Kubernetes pods are not yet protected
Kubernetes pods are not yet protected by ECI. A malicious or privileged pod can
compromise the Docker Desktop Linux VM and bypass security controls.
When using the Docker Desktop integrated Kubernetes, pods are not yet protected
by ECI. Therefore a malicious or privileged pod can compromise the Docker
Desktop Linux VM and bypass security controls.
As an alternative, you can use the [K8s.io KinD](https://kind.sigs.k8s.io/) tool
with ECI. In this case, each Kubernetes node runs inside an ECI-protected
container, thereby more strongly isolating the Kubernetes cluster away from the
underlying Docker Desktop Linux VM (and Docker Engine within). No special
arrangements are needed, just enable ECI and run the KinD tool as usual.
### Extension containers are not yet protected
@ -102,6 +109,13 @@ Desktop.
are not yet protected by ECI. We expect to improve on this in future versions of
Docker Desktop.
### Native Windows containers are not supported
ECI only works when Docker Desktop is in Linux containers mode (the default,
most common mode). It's not supported when Docker Desktop is configured in
native Windows containers mode (i.e., it's not supported on Windows hosts, when
Docker Desktop is switched from its default Linux mode to native Windows mode).
### Use in production
In general users should not experience differences between running a container