docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.42k stars 116 forks source link

Docker Desktop on Mac "applescript error- osascript- can't open default scripting component" #7002

Open PacoH opened 9 months ago

PacoH commented 9 months ago

Description

Re: Docker.app version 4.24.0 on OS X Ventura 13.3.1

Opened app and clicked button Finish setting up Docker Desktop version 4.24.0 (122432). Got Error: {"message" "applescript error: osascript: can't open default scripting component.\n"}.

Reproduce

  1. Run the app
  2. Get popup: Finish setting up Docker Desktop version 4.24.0 (122432)
  3. Use recommended settings (requires password) Docker Desktop automatically sets the necessary configurations that work for most developers. button automatically selected
  4. Click the button
  5. Get Error: {"message" "applescript error: osascript: can't open default scripting component.\n"}
  6. Select Use advanced settings You manually set your preferred configurations. button
  7. Get same results

Expected behavior

Expecetd Docker to just run, not run an Applescript component which either doesn't exist or was not properly opened.

docker version

Client: Docker Engine - Community
 Version:           24.0.6
 API version:       1.43
 Go version:        go1.21.0
 Git commit:        ed223bc820
 Built:             Thu Aug 31 17:24:32 2023
 OS/Arch:           darwin/amd64
 Context:           desktop-linux

docker info

Client: Docker Engine - Community
 Version:    24.0.6
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
  compose: Docker Compose (Docker Inc.)
  dev: Docker Dev Environments (Docker Inc.)
  extension: Manages Docker extensions (Docker Inc.)
  init: Creates Docker-related starter files for your project (Docker Inc.)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
  scan: Docker Scan (Docker Inc.)
  scout: Docker Scout (Docker Inc.)
Server:
ERROR: Cannot connect to the Docker daemon at unix:///$USER/.docker/run/docker.sock. Is the docker daemon running?

Diagnostics ID

E4AC5584-6875-4C02-9635-C69037B4448E/20230930144426

Additional Info

Starting diagnostics

[PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [PASS] DD0018: does the host support virtualization? [FAIL] DD0001: is the application running? Docker is not running [2023-09-30T14:48:43.615533000Z][com.docker.diagnose.ipc][W] (5adb6645) ac1c4a32-diagnose C<-S NoResponse POST /idle/make-busy (1.504435ms): Post "http://ipc/idle/make-busy": dial unix /Library/Containers/com.docker.docker/Data/backend.sock: connect: connection refused

[PASS] DD0017: can a VM be started? [FAIL] DD0016: is the LinuxKit VM running? prereq failed: is the application running? [FAIL] DD0011: are the LinuxKit services running? prereq failed: is the LinuxKit VM running? [FAIL] DD0004: is the Docker engine running? prereq failed: are the LinuxKit services running? [FAIL] DD0015: are the binary symlinks installed? 2 errors occurred:

TIERESAID commented 8 months ago

This issue is generally caused by Audio Plug-ins in the folder /Library/Audio/Plug-Ins/Components To identify third-party applications that might be interfering with your desktop configuration using the macOS Terminal : sudo dtruss -n osalang -t open

or you can delete all the element inside and you will see .

PacoH commented 8 months ago

Thanks for your reply.

sudo dtruss -n osalang -t open showed nothing when I tried to click 'Use recommended settings (requires password)' and it again failed. It issued the warning 'dtrace: system integrity protection is on, some features will not be available'.

I temporarily deleted the files in /Library/Audio/Plug-Ins/Components and that actually worked. I then replaced them and it opens now.

Please explain why a folder that has nothing to do with this app and is vital to the DAWs I have installed can cause an applescript error. I, like millions of stymied Macos users, have found that Ventura is so dysfunctional that it is probably responsible for such illogical behavior, but really…

azhinu commented 3 months ago

I have a same problem. macOS 12.5.1 Docker Desktop 4.28.0

I have a piano plugin in ~/Library/Audio/Plug-Ins/Components and some plugins in /Library/Audio/Plug-Ins/Components. When I removed piano plugin in ~/Library/Audio/Plug-Ins/Components, Docker Desktop password prompt started works. I didn't delete plugins in /Library/Audio/Plug-Ins/Components