Container Isolation and File Access FAQs in Docker Desktop

--- description: Find the answers to container security related FAQs keywords: Docker, Docker Hub, Docker Desktop security FAQs, platform, Docker Scout, admin, security title: Container security FAQs linkTitle: Container weight: 20 tags: [FAQ] aliases: - /faq/security/containers/ --- ### How are containers isolated from the host in Docker Desktop? Docker Desktop runs all containers inside a customized / minimal Linux virtual machine (except for native Windows containers). This adds a strong layer of isolation between containers and the host the machine, even if containers are running rootful. However note the following: * Containers have access to host files configured for file sharing via Settings -> Resources -> File Sharing (see the next FAQ question below for more info). * By default, containers run as root but with limited capabilities inside the Docker Desktop VM. Containers running with elevated privileges (e.g., `--privileged`, `--pid=host`, `--cap-add`, etc.) run as root with elevated privileges inside the Docker Desktop VM which gives them access to Docker Desktop VM internals, including the Docker Engine. Thus, users must be careful which containers they run with such privileges to avoid security breaches by malicious container images. * If [Enhanced Container Isolation (ECI)](/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/_index.md) mode is enabled, then each container runs within a dedicated Linux User Namespace inside the Docker Desktop VM, which means the container has no privileges within the Docker Desktop VM. Even when using the `--privileged` flag or similar, the container processes will only be privileged within the container's logical boundary, but unprivileged otherwise. In addition, ECI protects uses other advanced techniques to ensure they can't easily breach the Docker Desktop VM and Docker Engine within (see the ECI section for more info). No changes to the containers or user workflows are required as the extra protection is added under the covers. ### To which portions of the host filesystem do containers have read and write access? Containers can only access host files if these are shared via Settings -> Resources -> File Sharing, and only when such files are bind-mounted into the container (e.g., `docker run -v /path/to/host/file:/mnt ...`). ### Can containers running as root gain access to admin-owned files or directories on the host? No; host file sharing (bind mount from the host filesystem) uses a user-space crafted file server (running in `com.docker.backend` as the user running Docker Desktop), so containers can’t gain any access that the user on the host doesn’t already have.

This section answers frequently asked questions about container isolation and file access within Docker Desktop. It explains how containers are isolated from the host using a Linux virtual machine, the limitations on file access, and the implications of running containers with elevated privileges. It also discusses Enhanced Container Isolation (ECI) mode, which provides an additional layer of security by running each container in a dedicated Linux User Namespace. Finally, it clarifies how host file sharing works and whether containers running as root can access admin-owned files on the host.