Docker Desktop Warning - "Another application changed your Desktop configurations"

[solrevdev]

Description

I'm running Docker Desktop on macOS and keep getting the warning "Another application changed your Desktop configurations. This may cause unexpected behavior and errors." I reapply the configurations, but the message keeps coming back. I don't know what other application could be causing this and wonder if it's a known bug.

Reproduce

Not sure how to reproduce. Here are some screenshots which may help:

---

Expected behavior

No warnings from Docker Desktop about other applications changing my Desktop configurations.

docker version

Client:
 Cloud integration: v1.0.35
 Version:           24.0.2
 API version:       1.43
 Go version:        go1.20.4
 Git commit:        cb74dfc
 Built:             Thu May 25 21:51:16 2023
 OS/Arch:           darwin/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.21.0 (113844)
 Engine:
  Version:          24.0.2
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.4
  Git commit:       659604f
  Built:            Thu May 25 21:52:17 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.21
  GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:          1.1.7
  GitCommit:        v1.1.7-0-g860f061
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    24.0.2
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.0
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.19.0
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.6
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-scan
  scout: Command line tool for Docker Scout (Docker Inc.)
    Version:  0.16.1
    Path:     /Users/solrevdev/.docker/cli-plugins/docker-scout

Server:
 Containers: 3
  Running: 1
  Paused: 0
  Stopped: 2
 Images: 11
 Server Version: 24.0.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
 runc version: v1.1.7-0-g860f061
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.49-linuxkit-pr
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 7.676GiB
 Name: docker-desktop
 ID: 1d6e6445-8265-493a-b784-67720e5bf59d
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

Diagnostics ID

Diagnostics ID: 9D492876-F053-4E53-B9F7-58BF882254A8/20230630193135 (uploaded)

Additional Info

I ran the following diagnostic check:

/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
[2023-06-30T19:25:52.556360000Z][com.docker.diagnose.paths][I] set path configuration to OnHost
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?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[SKIP] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
No fatal errors detected.

All checks have passed, which generally indicates that my Docker installation is healthy.

Here is my system info:

OS: macOS 12.6.7 21G651 x86_64
Host: Macmini7,1
Kernel: 21.6.0
Uptime: 3 hours, 41 mins
Packages: 356 (brew)
Shell: zsh 5.8.1
Resolution: 1920x1080
DE: Aqua
WM: Quartz Compositor
WM Theme: Blue (Light)
Terminal: iTerm2
Terminal Font: CascadiaMonoPL-Regular 16
CPU: Intel i5-4278U (4) @ 2.60GHz
GPU: Intel Iris
Memory: 9810MiB / 16384MiB

I should add that I closed down all open apps and could see nothing that would realistically interfere with docker.

[yuowo39]

@yuowo39 @sunsetted @ryankert01 @millievn can you please share a diagnostics id?

521A3605-80CB-4D5F-9CB1-8C47B4B8ACDF/20240312141552

[hae-andrew-young]

same

[qeo-xx]

I had the same issue. Unfortunately, the steps suggested by @trevordcampbell didn't work for me.

Software Versions

macOS 12.7.4 Docker Desktop 4.28.0 (139021)

The following workaround helped me:

1. Check the docker logs for symlink issues like: log stream --predicate 'eventMessage contains "docker" and eventMessage contains "symlink"'

in my case the following was in the log: symlink /usr/local/bin/docker-credential-ecr-login is pointing to /usr/local/Caskroom/docker/4.28.0,139021/Docker.app/Contents/Resources/bin/docker-credential-ecr-login , expected parent dir: /Applications/Docker.app/Contents/Resources/bin

2. Fix symlink manually: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

[millievn]

Same issue

occur after i uninstall orbstack. reinstall docker some times and symlink (not know which one helps but it works now)

ln -s ~/.docker/run/docker.sock /var/run/docker.sock

[placeposition]

Same issue- this happens when I stop my containers and open up MAMP to work on another (old) project. Then II close down MAMP and start my containers again- they all start but I have no connectivity between my php container and the mysql container.

I fix it by restarting the mac and re-applying the configuration.

Mac OS Sonoma Version 14.3.1 Docker Desktop 4.28.0

[Asma-Djehiche]

I had the same issue. Unfortunately, the steps suggested by @trevordcampbell didn't work for me.

Software Versions

macOS 12.7.4 Docker Desktop 4.28.0 (139021)

The following workaround helped me:

1. Check the docker logs for symlink issues like: log stream --predicate 'eventMessage contains "docker" and eventMessage contains "symlink"'

in my case the following was in the log: symlink /usr/local/bin/docker-credential-ecr-login is pointing to /usr/local/Caskroom/docker/4.28.0,139021/Docker.app/Contents/Resources/bin/docker-credential-ecr-login , expected parent dir: /Applications/Docker.app/Contents/Resources/bin

2. Fix symlink manually: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

@qeo-xx Thank you, your method worked for me too 👌 (MacOS: Sonoma 14.3.1 and Docker: 4.28.0)

[reybis]

@tangix @mortonmj @ViggoV @clemsau I may have found a workaround for the issue where the /var/run/docker.sock file is not persisting...

I've just set up an new mac, and playing around with all the settings. It seems like this is Docker Desktop mishandling the saving of the file on app shutdown.

There's a setting on Mac for persisting windows when quitting an application – by default my new mac had that setting turned ON. I was playing around to see if maybe this was the root cause of the issue with Docker Desktop... and it seems like I might have fixed this issue for myself? Here's what I did that ended up working for me.

MacOS Workaround Steps: (Sonoma 14.2.1)

1. Fresh boot of computer, nothing else open.
2. Turn the Mac "Close windows when closing an application" setting to OFF. ( -> System Settings -> Desktop & Dock -> "Close windows when quitting an application")

3. Launch Docker Desktop.
4. Receive the "Another application changed your Desktop configurations" prompt, click the Re-Apply button and resolve until it goes away.
5. Close + Terminate Docker Desktop app.
6. Reopen + Verify that no configuration prompt is received.
7. Turn the Mac "Close windows when closing an application" setting back to ON. ( -> System Settings -> Desktop & Dock -> "Close windows when quitting an application")

8. Power off Mac + restart.
9. Open Docker Desktop + Verify that no configuration prompt is received.

It seems like you only have to do this once for the /var/run/docker.sock file to finally persist and be maintained from that point forward, as I have not had the configuration error again after doing this.

Wondering if this will work for others too?

Thank you, your method worked for me!

[nakroy]

I had the same issue. Unfortunately, the steps suggested by @trevordcampbell didn't work for me.

Software Versions

macOS 12.7.4 Docker Desktop 4.28.0 (139021)

The following workaround helped me:

1. Check the docker logs for symlink issues like: log stream --predicate 'eventMessage contains "docker" and eventMessage contains "symlink"'

in my case the following was in the log: symlink /usr/local/bin/docker-credential-ecr-login is pointing to /usr/local/Caskroom/docker/4.28.0,139021/Docker.app/Contents/Resources/bin/docker-credential-ecr-login , expected parent dir: /Applications/Docker.app/Contents/Resources/bin

2. Fix symlink manually: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

I used the first command you provided to check the log message, but I didn't get the message including "docker-credential-ecr-login". So I checked the path in /usr/local/bin/, and I couldn't find the docker-credential-ecr-login file, but I found this file in /Applications/Docker.app/Contents/Resources/bin.

So obviously the problem is that this file is missing or not automatically creating a symbolic link in /usr/local/bin, and I used your second command to create a symbolic link of this file, it finally worked and the warning never shows again.

Thanks for your help

[0x1orz]

Docker Desktop 4.28.0 (139021) always raise the same issue

[nakroy]

Docker Desktop 4.28.0 (139021) always raise the same issue

If your platform is Apple Silicon MacOs, you can try:

1. check out whether these files are in /usr/local/bin: com.docker.cli docker-index docker docker-compose docker-credential-desktop kubectl docker-credential-ecr-login kubectl.docker docker-credential-osxkeychain
2. use ln -sf /Applications/Docker.app/Contents/Resources/bin/xxx /usr/local/bin/xxx command to create a symbolic link for the missing file, xxx is the file not in /usr/local/bin/

[brambregman]

Same issue here. For me, docker-credential-ecr-login seemed to be missing, but adding it did not resolve the problem.

[glassd]

I also had docker-credential-ecr-login missing. Adding that link immediately corrected the issue.

[tangentsoft]

Here, the docker-credential-ecr-login link wasn't missing outright but was pointed off into /opt/homebrew because I installed Docker Desktop as a Brew Cask. Re-pointing that link into /Applications as above fixed the symptom.

[OktarinTentakel]

adding docker-credential-ecr-login in /usr/local/bin seems to be the solution for me

[hae-andrew-young]

Yes. This worked for me as well.

[andbladi]

I wish we could take a poll and see how many of us installed via homebrew -- this is clearly the issue, was for me at least.

[ramsey]

I wish we could take a poll and see how many of us installed via homebrew -- this is clearly the issue, was for me at least.

Same for me, too.

[OktarinTentakel]

Yeah. Was installed from Homebrew.

[glassd]

I did not use homebrew. I installed from the website download.

[andbas]

Thanks @nakroy, noticed missed docker-credential-ecr-login

ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

Fixed the problem. Installation was done of a fresh MacOS thought official .dmg package. No homebrew installed on machine.

[jamshid]

In my case I already had the docker-credential-ecr-login symlink in /usr/local/bin/. But I also had a /usr/local/bin/docker-machine installed by brew (yes I still use it, still works still great). Once I removed that the mysterious and annoying Docker menu bar warning went away.

[koofree]

Thanks @nakroy, noticed missed docker-credential-ecr-login

ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

Fixed the problem. Installation was done of a fresh MacOS thought official .dmg package. No homebrew installed on machine.

I resolved by this solution. Thanks

[Khanivore73]

Thanks @nakroy, noticed missed docker-credential-ecr-login

ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

Fixed the problem. Installation was done of a fresh MacOS thought official .dmg package. No homebrew installed on machine.

Same here. A clean Ventura 13.6.5 on M2 Mac mini, a fresh copy of Docker 4.28.0 img and I was still getting this problem (#6898) which was resolved by doing the above command. Nice one @nakroy.

[aurnik]

I had this same issue and checked the logs as recommended by @qeo-xx and for me the symlink needed to be created in ~/.docker/bin, not /usr/local/bin. Everything is working as expected now.

macOS Ventura 13.6.3 on an M2 Pro, Docker installed via .dmg from website.

[jriff]

I have the same problem. I downloaded Docker for my M3 Mac from the Docker website.

[BenjaminGittins]

Disabling a feature is not a solution. I have the same problem on a clean installation of Docker Desktop on macos 14.3.1 for intel. Please fix

[ArianHamdi]

Same problem. MacOS 14.4 with m2 chip and fresh installation of the Docker desktop.

[Khanivore73]

Out of curiousity I again tonight did a completely fresh install of Ventura 13.6.5 on my Mac Mini M2 and first thing I did was download and install a fresh copy of Docker 4.28.0 IMG file. Immediately after install I launch Docker and I get the same problem.

Currently this is the only solution via Terminal:

sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

[headkit]

same same on M3

[ViggoV]

Interesting. The symlink solution as mentioned by a few people in this thread worked for me, but the error still showed on startup for a minute or two before disappearing.

[cicorias]

why is this issued closed? the symlink fixes this issue sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

[CyrilJohnson]

I have not checked Automatically check configuration checkbox in settings, but that turned out not to matter, at least to me, and accordingly, I'm only a User for CLI tools configuration, so this symlink worked for me: sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login ~/.docker/bin/docker-credential-ecr-login MacBook Pro (M1 Pro)

[Blankeos]

Thank you for the symlink solution. Machine: Sonoma Version 14.3 | MBP M3 Max

[shanesmith]

The missing docker-credential-ecr-login issue (and annoying warning) should hopefully be fixed for the Homebrew folks by https://github.com/Homebrew/homebrew-cask/pull/169634

[sirbots]

When I re-applied the config settings, docker stopped working in my terminal. I fixed it by going to Docker > Advanced Settings and checking "System default" under Choose container terminal.

[cltalmadge]

Here, the docker-credential-ecr-login link wasn't missing outright but was pointed off into /opt/homebrew because I installed Docker Desktop as a Brew Cask. Re-pointing that link into /Applications as above fixed the symptom.

I was missing this link, as well. However, I installed Docker through the DMG, not Homebrew.

[dielsonsales]

why is this issued closed? the symlink fixes this issue sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

Apparently the check was disabled at some point but reappeared in a subsequent version. Seems like there is a new issue opened: https://github.com/docker/for-mac/issues/7208 and the problem will be fixed in the next release.

Commenting here because Google has been directing people with this issue to this thread.

[greenflute]

me with the same issue, and the ecr-login was linked to homebrew:

% ls -lha /usr/local/bin/docker-credential-ecr-login lrwxr-xr-x 1 … ... 102B Feb 29 16:22 /usr/local/bin/docker-credential-ecr-login -> /usr/local/Caskroom/docker/4.28.0,139021/Docker.app/Contents/Resources/bin/docker-credential-ecr-login

and after force reinstall in homebrew it became this: ls -lha /usr/local/bin/docker-credential-ecr-login lrwxr-xr-x 1 … ... 75B Mar 29 11:27 /usr/local/bin/docker-credential-ecr-login -> /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login

but this issue is not solved, that message is still there.

[crmcmullen]

I had this same error. I am on a Macbook Pro Intel chip. I also installed Docker with a download from their website on a fresh MacOS Sonoma install, not using Homebrew.

The issue was resolved by copying the symlink over as described. Now I do not get the osascript error anymore and I do not have to uncheck the "Automatically check configuration" setting in Advanced Settings in Docker Desktop.

[pankaj0825]

Hello

The check can be disabled in Advanced Settings

Thanks

[edupmon]

Also confirming that on an M1 Mac with Sonoma 14.4.1 with only xcode command line tools and docker desktop 4.28.0 installed the symlink workaround mentioned above, fixed the issue:

sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

[SunnyVats0103]

I faced same issue on an Intel MacBook Pro with current latest OS.

Steps I accidentally did, to create this issue:

1. Uninstalled existing docker using System Settings > General > Storage > Docker > Remove. (to upgrade to new one as upgrading to latest version from Docker Desktop takes infinite amount of time)
2. Tried to install using brew commands: brew install docker brew install --casks docker
3. These steps modified some files in /usr/local/bin and there were some files from previous Docker installation still linked to /Application/Docker.app deleted directory.
4. Installed latest docker on my system and warning started coming.

Steps I performed to resolve the issue:

1. Closed running docker app.
2. Searched for any symlink with name docker in /usr/local/bin with wrong reference or older reference.
3. Deleted older reference and pointed again to same directory.
4. Searched for symlink kubectl* and hub-tool in same directory and deleted them.
5. Pointed symlink to latest docker app directory.
6. Started docker app and the issue was resolved.

[josealbertomartinezvi]

I had the same issue. Unfortunately, the steps suggested by @trevordcampbell didn't work for me.

Software Versions

macOS 12.7.4 Docker Desktop 4.28.0 (139021)

The following workaround helped me:

1. Check the docker logs for symlink issues like: log stream --predicate 'eventMessage contains "docker" and eventMessage contains "symlink"'

in my case the following was in the log: symlink /usr/local/bin/docker-credential-ecr-login is pointing to /usr/local/Caskroom/docker/4.28.0,139021/Docker.app/Contents/Resources/bin/docker-credential-ecr-login , expected parent dir: /Applications/Docker.app/Contents/Resources/bin

2. Fix symlink manually: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

Excellent, Thank you.

[zarfmouse]

It looks like on my system the issue is that when you use the "Re-apply configurations" menu item it doesn't even try to create the missing docker-credential-ecr-login symlink. I kept getting the error after making the symlink in /usr/local/bin and discovered from the logs that the symlinks need to be in $HOME/.docker/bin. Putting the symlink there fixed the error.

So the bug here seems to be that the health check looks for this symlink but the installer and/or the "Re-apply configurations" functions don't put the symlink in place.

This is version 4.28.0

Below is the log of what it tries to do when re-applying configuration. Notice that it doesn't contain any reference to the docker-credential-ecr-login command.

sh-3.2# log stream --predicate 'eventMessage contains "docker" and eventMessage contains "symlink"'
Filtering the log data using "composedMessage CONTAINS "docker" AND composedMessage CONTAINS "symlink""
Timestamp                       Thread     Type        Activity             PID    TTL  
2024-04-02 13:09:50.128432-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-buildxpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-buildx
2024-04-02 13:09:50.128676-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-composepoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-compose
2024-04-02 13:09:50.128860-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-debugpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-debug
2024-04-02 13:09:50.129204-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-devpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-dev
2024-04-02 13:09:50.129477-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-extensionpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-extension
2024-04-02 13:09:50.129742-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-feedbackpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-feedback
2024-04-02 13:09:50.129981-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-initpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-init
2024-04-02 13:09:50.130339-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-sbompoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-sbom
2024-04-02 13:09:50.130587-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-scoutpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-scout
2024-04-02 13:09:50.131441-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-buildxpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-buildx
2024-04-02 13:09:50.131636-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-composepoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-compose
2024-04-02 13:09:50.131836-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-debugpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-debug
2024-04-02 13:09:50.132060-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-devpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-dev
2024-04-02 13:09:50.133757-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-extensionpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-extension
2024-04-02 13:09:50.133922-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-feedbackpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-feedback
2024-04-02 13:09:50.134020-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-initpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-init
2024-04-02 13:09:50.134125-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-sbompoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-sbom
2024-04-02 13:09:50.134382-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/cli-plugins/docker-scoutpoints to/Applications/Docker.app/Contents/Resources/cli-plugins/docker-scout
2024-04-02 13:09:50.141536-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/dockerpoints to/Applications/Docker.app/Contents/Resources/bin/docker
2024-04-02 13:09:50.141651-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/com.docker.clipoints to/Applications/Docker.app/Contents/Resources/bin/com.docker.cli
2024-04-02 13:09:50.142624-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/docker-composepoints to/Applications/Docker.app/Contents/Resources/bin/docker-compose
2024-04-02 13:09:50.143673-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/hub-toolpoints to/Applications/Docker.app/Contents/Resources/bin/hub-tool
2024-04-02 13:09:50.144625-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/docker-indexpoints to/Applications/Docker.app/Contents/Resources/bin/docker-index
2024-04-02 13:09:50.145612-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/docker-credential-desktoppoints to/Applications/Docker.app/Contents/Resources/bin/docker-credential-desktop
2024-04-02 13:09:50.145763-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/docker-credential-osxkeychainpoints to/Applications/Docker.app/Contents/Resources/bin/docker-credential-osxkeychain
2024-04-02 13:09:50.146289-0500 0xb2a01    Default     0x0                  18028  0    com.docker.backend: symlink<HOME>/.docker/bin/kubectl.dockerpoints to/Applications/Docker.app/Contents/Resources/bin/kubectl

[zakariasassi]

I had the same issue

i removed the check sign from the Automatically check configuration option from advance settings now it work fine !

[panique]

One year later and the error still exists on freshly installed latest Docker on macOS :/

And why the heck is any other app (which?) even able to change configs of such an important tool? Docker is the core of our development process, and it's broken in every aspect, it's nuts how much time we spend just trying to get it running correctly all the time, even on a fresh new system basic things like buiilding a simple container dont work anymore out of the box...

[fharper]

Just want to be clear here... I also disabled the "automatically check configuration" feature to prevent that annoying message, but it is not a solution to the issue. It's more like a workaround.

It would be nice to know what was modified, and if possible, which application modified it, as stated many times in this thread.

[cyhsu]

Using sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login solved the issue.

Mine is M3, Sonoma 14.4.1, docker installed from docker official website.

[c-ameron]

FYI, uninstalling and reinstalling with the older version 4.27.2 (then updating) works.

https://github.com/docker/for-mac/issues/7208#issuecomment-2033880837

[krzysztof-ziemacki]

Using sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login solved the issue.

Mine is M3, Sonoma 14.4.1, docker installed from docker official website.

Thank you so much @cyhsu. It worked for me flawlessly!