Ensuring localhost and are defined in /etc/hosts.The so-called “privileged ports” have not generally been used as a security boundary, however OSes still prevent unprivileged processes from binding them which breaks commands like docker run -p 80:80 nginx Binding privileged ports that are less than 1024.This ensures the docker CLI is on the user’s PATH without having to reconfigure shells, log out then log back in for example. Installing and uninstalling symlinks in /usr/local/bin.The Docker Desktop backend communicates with it over the UNIX domain socket /var/run/. The privileged helper is started by launchd and runs in the background unless it is disabled at runtime as previously described. Spindump diagnostics for fine grained CPU utilization are not gathered.The containers will run but the port won’t be exposed on the host. Docker Desktop can only be run by one user account per machine, namely the one specified in the -–user flag.This approach has the following limitations: Ensures that localhost and are present in /etc/hosts.In this case, the user will not be prompted to grant root privileges on the first run of Docker Desktop. This will result in being used for set up during installation and then disabled at runtime. In version 4.11 and above of Docker Desktop for Mac you can avoid running the privileged helper service in the background by using the -user flag on the install command. This approach allows, following the principle of least privilege, root 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. The reason for this is that Docker Desktop needs to perform a limited set of privileged operations using the privileged helper process. For subsequent runs, no root privileges are required. The first time that Docker Desktop is launched the user receives an admin prompt to grant permissions for a privileged helper service to be installed. In the default set up flow, Docker Desktop for Mac does not require root privileges for installation but does require root access to be granted on the first run. It also provides clarity on 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 and the reasoning behind this approach. Understand permission requirements for Mac

Close docker on mac