From db737b2bfb7b34577f5c32a790d8ff2a479d5f49 Mon Sep 17 00:00:00 2001 From: todd densmore <469399+tdensmore@users.noreply.github.com> Date: Thu, 4 Jan 2024 10:33:05 -0500 Subject: [PATCH] Update how-eci-works.md (#19034) Some edits for clarity --- .../enhanced-container-isolation/how-eci-works.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md b/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md index 9aae36b084..2aee31cafd 100644 --- a/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md +++ b/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md @@ -8,9 +8,9 @@ keywords: set up, enhanced container isolation, rootless, security > > Enhanced Container Isolation is available to Docker Business customers only. -Enhanced Container Isolation hardens container isolation using the [Sysbox +Docker implements Enhanced Container Isolation by using the [Sysbox container runtime](https://github.com/nestybox/sysbox). Sysbox is a fork of the -standard OCI runc runtime that was modified to enhance container isolation and +standard OCI runc runtime that was modified to enhance standard container isolation and workloads. For more details see [Under the hood](#under-the-hood). Starting with version 4.13, Docker Desktop includes a customized version of @@ -91,4 +91,4 @@ and creates a stronger boundary between the containers and the Docker Engine. Enhanced Container Isolation is meant to ensure containers launched with Docker Desktop can't easily breach the Docker Desktop Linux VM and therefore modify -security settings within it. \ No newline at end of file +security settings within it.