ENGDOCS-924 (#15468)

This commit is contained in:
Allie Sadler 2022-08-25 16:53:05 +01:00 committed by GitHub
parent 04c34b9637
commit 56c9827312
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 17 additions and 14 deletions

View File

@ -1122,10 +1122,14 @@ manuals:
section:
- path: /desktop/install/mac-install/
title: Install on Mac
- path: /desktop/mac/apple-silicon/
title: Install on Apple silicon
- path: /desktop/mac/permission-requirements/
title: Understand permission requirements for Mac
- path: /desktop/install/windows-install/
title: Install on Windows
- path: /desktop/windows/permission-requirements/
title: Understand permission requirements for Windows
- path: /desktop/mac/apple-silicon/
title: Install on Apple silicon
- path: /desktop/install/linux-install/
title: Install on Linux
- sectiontitle: Installation per Linux distro
@ -1178,10 +1182,6 @@ manuals:
title: Back up and restore data
- path: /desktop/networking/
title: Explore networking features
- path: /desktop/mac/permission-requirements/
title: Docker Desktop permission requirements for Mac
- path: /desktop/windows/permission-requirements/
title: Docker Desktop permission requirements for Windows
- path: /desktop/windows/wsl/
title: Docker Desktop WSL 2 backend on Windows
- path: /desktop/vm-vdi/

View File

@ -1,13 +1,15 @@
---
description: Permission requirements for Docker Desktop for Mac
keywords: Docker Desktop, mac, security, install
title: Docker Desktop permission requirements for Mac
title: Understand permission requirements for Mac
redirect_from:
- /docker-for-mac/privileged-helper/
- /desktop/mac/privileged-helper/
---
This page contains information about the permission requirements for running and installing Docker Desktop on Mac, the functionality of the privileged helper process `com.docker.vmnetd` and the reasoning behind this approach, as well as clarification about running containers as `root` as opposed to having `root` access on the host.
This page contains information about the permission requirements for running and installing Docker Desktop on Mac, the functionality of the privileged helper process `com.docker.vmnetd` and the reasoning behind this approach.
It also provides clarity on running containers as `root` as opposed to having `root` access on the host.
## Permission requirements

View File

@ -1,16 +1,18 @@
---
description: Permission requirements for Docker Desktop for Windows
keywords: Docker Desktop, Windows, security, install
title: Docker Desktop permission requirements for Windows
title: Understand permission requirements for Windows
redirect_from:
- /desktop/windows/privileged-helper/
---
This page contains information about the permission requirements for running and installing Docker Desktop on Windows, the functionality of the privileged helper process `com.docker.service.exe` and the reasoning behind this approach, as well as clarification about running containers as `root` as opposed to having `Administrator` access on the host and the privileges of the Windows Docker engine and Windows containers.
This page contains information about the permission requirements for running and installing Docker Desktop on Windows, the functionality of the privileged helper process `com.docker.service.exe` and the reasoning behind this approach.
It also provides clarity on running containers as `root` as opposed to having `Administrator` access on the host and the privileges of the Windows Docker engine and Windows containers.
## Permission requirements
While Docker Desktop can be run without having `Administrator` privileges, it does require them during installation. On installation the user gets an UAC prompt which allows a privileged helper service to be installed. After that Docker Desktop can be run by users without Administrator privileges, provided that they are members of the `docker-users` group. The user who performs the installation is automatically added to this group, but other users must be added manually. This allows the administrator to control who has access to Docker Desktop.
While Docker Desktop on Windows can be run without having `Administrator` privileges, it does require them during installation. On installation the user gets a UAC prompt which allows a privileged helper service to be installed. After that, Docker Desktop can be run by users without administrator privileges, provided they are members of the `docker-users` group. The user who performs the installation is automatically added to this group, but other users must be added manually. This allows the administrator to control who has access to Docker Desktop.
The reason for this approach is that Docker Desktop needs to perform a limited set of privileged operations which are conducted by the privileged helper process `com.docker.service.exe`. This approach allows, following the principle of least privilege, `Administrator` access to be used only for the operations for which it is absolutely necessary, while still being able to use Docker Desktop as an unprivileged user.
@ -31,7 +33,6 @@ The service performs the following functionalities:
- Checking if required Windows features are both installed and enabled.
- Conducting healthchecks and retrieving the version of the service itself.
## Containers running as root within the Linux VM
The Linux Docker daemon and containers run in a minimal, special-purpose Linux VM managed by Docker. It is immutable so users cant extend it or change the installed software.