Install Docker Desktop silently on Mac

[arthurgallaghersr]

We are attempting to deploy/install Docker Desktop on MacBook Pro (MacOS).

We are getting two different pop-up messages...

The first pop-up that appears is "Docker is an app downloaded from the Internet. Are you sure you want to open it?"

The second pop-up that appears is "Docker Desktop needs privileged access."

We need assistance with the terminal commands/switches/scripting that will suppress these pop-up messages so that we can silently deploy this application.

[thaJeztah]

Do the instruction in Install from the command line help?

[firien]

It would be nice to be able to install without admin password. Is this solely to access ports <1024?
If so, it would be nice to allow install without admin password - and prompt to install this helper only if a user attempts to map a <1024 port.

[thaJeztah]

@firien I think that's being worked on; see docker/roadmap#383

[JtMotoX]

I am also running into this issue each time there is an update. I perform brew upgrade; brew upgrade --cask --greedy; which updates docker to the latest version but when I run open /Applications/Docker.app after the update is finished, it will not launch because of these 2 pop-ups. I have to then RDP into the machines and manually go through these pop-ups. This gets very annoying every time we have to perform updates on these machines.

It would be better if the brew update process asked for the admin password during installation (similar to how the Powershell update via brew works).

[docker-robott]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, add a comment on this issue.
If not, this issue will be closed in 30 days.

Mark the issue as fresh with a /remove-lifecycle stale comment.
Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked