Skip to content

Commit 85c6fab

Browse files
authored
Apply suggestions from code review
1 parent 7b06a21 commit 85c6fab

File tree

1 file changed

+5
-5
lines changed
  • content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation

1 file changed

+5
-5
lines changed

content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/faq.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -71,18 +71,18 @@ Not yet. It protects all containers launched by users via `docker create` and
7171

7272
For containers implicitly created by `docker build` as well as Docker
7373
Desktop's integrated Kubernetes, protection varies depending on the Docker
74-
Desktop version (see the next two FAQs below).
74+
Desktop version (see the following two FAQs).
7575

7676
ECI does not yet protect Docker Desktop Extension containers and
7777
[Dev Environments containers](/manuals/desktop/features/dev-environments/_index.md).
7878

79-
### Does ECI protect containers implicitly used by "docker build"?
79+
### Does ECI protect containers implicitly used by `docker build`?
8080

8181
Prior to Docker Desktop 4.19, ECI did not protect containers used implicitly
8282
by `docker build` during the build process.
8383

8484
Since Docker Desktop 4.19, ECI protects containers used by `docker build`
85-
when using the [docker-container build driver](/manuals/build/builders/drivers/_index.md).
85+
when using the [Docker container build driver](/manuals/build/builders/drivers/_index.md).
8686

8787
In addition, since Docker Desktop 4.30, ECI also protects containers used by
8888
`docker build` when using the default "docker" build driver, on all
@@ -94,13 +94,13 @@ Prior to Docker Desktop 4.38, ECI did not protect the Kubernetes cluster
9494
integrated in Docker Desktop.
9595

9696
Since Docker Desktop 4.38, ECI protects the integreated Kubernetes cluster
97-
when using the new "kind" provisioner (see [Deploy On Kubernetes](../../../../desktop/features/kubernetes.md)).
97+
when using the new **kind** provisioner (see [Deploy On Kubernetes](/manuals/desktop/features/kubernetes.md)).
9898
In this case, each node in the multi-node Kubernetes cluster is actually an ECI
9999
protected container. With ECI disabled, each node in the Kubernetes cluster is
100100
a less-secure fully privileged container.
101101

102102
ECI does not protect the integrated Kubernetes cluster when using the
103-
older "Kubeadm" provisioner (single-node cluster).
103+
older **Kubeadm** single-node cluster provisioner.
104104

105105
### Does ECI protect containers launched prior to enabling ECI?
106106

0 commit comments

Comments
 (0)