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

solrevdev · 2023-06-30T19:34:41Z

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.

tksrc · 2023-07-01T10:57:16Z

Same here

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/arm64
 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:50:59 2023
  OS/Arch:          linux/arm64
  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/teo/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.19.0
    Path:     /Users/teo/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/teo/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/teo/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.6
    Path:     /Users/teo/.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/teo/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/teo/.docker/cli-plugins/docker-scan
  scout: Command line tool for Docker Scout (Docker Inc.)
    Version:  0.16.1
    Path:     /Users/teo/.docker/cli-plugins/docker-scout

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 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: aarch64
 CPUs: 5
 Total Memory: 23.45GiB
 Name: docker-desktop
 ID: 2616eea7-bdaf-4cd6-be36-d2a4a602e181
 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

carrete · 2023-07-02T14:14:56Z

Same. I've uninstalled and re-installed several times, still same behavior

See also https://stackoverflow.com/questions/76586460/i-get-the-following-error-in-docker-desktop-for-mac

bitbemol · 2023-07-03T03:27:58Z

Same issue

tkm5 · 2023-07-03T05:56:41Z

I have the same issue.

I ran the following command, deleted all docker related files, and reinstalled.
and reinstalled it, but the problem persists.

sudo rm -rf ~/.docker
sudo rm -rf ~/Library/Containers/com.docker.docker
sudo rm -rf ~/Library/Group\ Containers/group.com.docker
sudo rm -rf ~/Library/Caches/com.docker.docker
sudo rm -rf /Library/PrivilegedHelperTools/com.docker.vmnetd
sudo rm -rf /Library/LaunchDaemons/com.docker.vmnetd.plist
sudo rm -rf /usr/local/lib/docker
sudo rm -rf ~/Library/Application\ Support/Docker\ Desktop
sudo rm -rf ~/Library/Preferences/com.docker.docker.plist
sudo rm -rf ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState
sudo rm -rf ~/Library/Group\ Containers/group.com.docker
sudo rm -rf ~/Library/Logs/Docker\ Desktop
sudo rm -rf ~/Library/Preferences/com.electron.docker-frontend.plist
sudo rm -rf ~/Library/Cookies/com.docker.docker.binarycookies

sbrosgol · 2023-07-03T06:42:15Z

same here, very annoying... :-(

dwzrlp · 2023-07-03T14:02:51Z

me too

lorenrh · 2023-07-03T16:58:13Z

Thanks for your feedback!
we've released Docker Desktop 4.21.1 that disables the feature for further investigation. Check out https://docs.docker.com/desktop/release-notes/

I'll close this issue for now!

AnilG3 · 2023-09-18T01:59:51Z

Is there a way to disable health check? It appears the same issue is back with 4.23.0 upgrade.

der-Lehmann · 2023-09-18T07:24:30Z

I am on version 4.23.0 (120376) and I also receive the mentioned notice.
However I have two user accounts on my macbook. Both of them have docker desktop installed.
So I assume that the configs get changed whenever I start docker desktop with the opposite user.

solrevdev · 2023-09-18T08:47:16Z

Yes it's returned for me too on Docker Desktop 4.23.0 (120376). I've opened issue #6982 to get attention

lorenrh · 2023-09-18T10:57:37Z

Hello

The check can be disabled in Advanced Settings

solrevdev · 2023-09-18T11:20:17Z

Hello

The check can be disabled in Advanced Settings

Brilliant thank you @lorenrh

jamshid · 2023-09-18T19:28:19Z

Sure is annoying to see "Configs changed by another App" and "Re-apply configurations" without any indication of what configs were changed. Docker Desktop 4.23.0 (120376) on Mac.

silverdr · 2023-09-19T11:40:33Z

Sure is annoying to see "Configs changed by another App" and "Re-apply configurations" without any indication of what configs were changed. Docker Desktop 4.23.0 (120376) on Mac.

Or what would be "re-applied" if one decides to go for it. And no, disabling the check is not a solution :-(

kcaashish · 2023-09-20T06:48:06Z

I am on a multiuser setup and have check checked User under Advanced settings and have ~/.docker/bin in the path for both the users. But I still get this every time I switch users.

wAuner · 2023-09-27T05:31:23Z

why is this closed when the issue still persists?
Seems to me that the check or at least its UI/user communication needs to be fixed.

bsousaa · 2023-09-27T11:54:32Z

@wAuner can you confirm what version of Docker Desktop you are running and share a diagnostics ID?

jaichinger · 2023-09-28T03:43:56Z

I noticed on my system (macOS 14.0) that /var/run/docker.sock is always missing on reboot. In the advanced settings of the desktop app, the option to Allow the default Docker socket to be used was ticked. When I correct the issue in the docker app, it recreates the socket.

I don't use any third-party clients that need the docker socket, so I unticked it and now don't get the warning. It lets me keep the config check enabled.

jirsbek · 2023-10-03T16:48:16Z

Having the same warning after OS startup I've noticed the warning is actually gone after about a minute so it doesn't bother me that much. Anyway I've turned the setting off as mentioned in #6898 (comment).

der-Lehmann · 2023-10-03T17:50:19Z

I also turned of the setting.
However when I did that, PHPStorm was no longer able to execute commands inside of a docker container. It failed saying that it could not connect to the docker socket.
When I enabled the setting and re-applied the configuration PHPStorm could execute commands again.

ViggoV · 2023-10-06T06:14:20Z

I am seeing this as well on MacOS Sonoma. /var/run/docker.sock is not created until i click the re-apply option (which requires me to enter my root password), so it appears that it is removed by MacOS on reboot and requires permission to recreate.

The re-apply settings option is a lot more elegant than an error pop-up on startup (which have been an annoyance earlier) but it would be really nice with a bit more info.

dielsonsales · 2024-03-28T20:44:28Z

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: #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 · 2024-03-29T10:22:45Z

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 · 2024-03-29T20:14:02Z

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 · 2024-03-30T17:54:58Z

Hello

The check can be disabled in Advanced Settings

Thanks

edupmon · 2024-03-31T11:09:38Z

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 · 2024-04-01T03:03:58Z

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

Steps I accidentally did, to create this issue:

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)
Tried to install using brew commands:
brew install docker
brew install --casks docker
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.
Installed latest docker on my system and warning started coming.

Steps I performed to resolve the issue:

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

josealbertomartinezvi · 2024-04-01T20:18:48Z

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:

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

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 · 2024-04-02T18:17:06Z

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 · 2024-04-03T20:45:57Z

I had the same issue

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

panique · 2024-04-04T16:23:09Z

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 · 2024-04-04T21:49:28Z

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 · 2024-04-05T14:12:27Z

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 · 2024-04-05T17:49:08Z

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

#7208 (comment)

krzysztof-ziemacki · 2024-04-06T08:08:49Z

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!

seanbethard · 2024-04-06T12:07:43Z

@cyhsu @krzysztof-ziemacki the link eliminates this cryptic warning for me too but it doesn't persist between boots.

amadorssa · 2024-04-08T19:06:39Z

"This worked for me. Honestly, I'm not sure how safe it is to give Docker developer permissions, but it solved the problem."

petersg83 · 2024-04-09T12:00:50Z

Same problem here with the latest version "Docker version 25.0.3, build 4debf41" I just installed. Please reopen the issue.

bsousaa · 2024-04-09T12:01:51Z

Can you please test with the latest Docker Desktop 4.29?

julioromano · 2024-04-09T12:12:18Z

4.29 fixed it for me, though in /usr/local/bin there is still no docker-credential-ecr-login file (not sure if this is intended or not).

tomson611 · 2024-04-09T20:44:17Z

4.29 fixed the issue for me

jvindel · 2024-04-10T20:53:38Z

4.29 fixed the issue for me too

PeterCai7 · 2024-04-11T15:15:09Z

4.29 fixed the issue

lilian-miakito · 2024-04-12T07:54:27Z

Same here, finally. I think we can mark this closed.

…

On Thu, Apr 11, 2024 at 17:15:39, Ju < ***@***.*** > wrote: 4.29 fixed the issue — Reply to this email directly, view it on GitHub ( #6898 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AYMNJEWI5HNCWRXWBL4LNKTY42SJXAVCNFSM6AAAAAAZ2HNR7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZHEZTKMRXGY ). You are receiving this because you commented. Message ID: <docker/for-mac/issues/6898/2049935276 @ github. com>

Gruven · 2024-04-25T07:11:56Z

MacOS 14.4.1, Docker 4.29 from official website. The same issue. Symlink doesn't help

napa3um · 2024-05-01T22:37:37Z

It seems to be somehow related (after re-apply, the exclamation mark disappears):

ALFmachine · 2024-05-09T21:53:17Z

this issue still exists for me on version 4.29.0

EvanPoe · 2024-05-16T02:38:49Z

On 4.29.0, and the issue persists. I actually can't upgrade to 4.30.0 either. I keep hitting update and restart, the application restarts, and it says Another application changed your Desktop configurations. This may cause unexpected behavior and errors." across the top and "New version available" on the bottom

solrevdev added the needs-triage label Jun 30, 2023

docker-robot bot added the version/4.21.0 label Jun 30, 2023

bsousaa added area/gui status/needs-investigating and removed needs-triage labels Jul 1, 2023

bsousaa added status/acknowledged and removed status/needs-investigating labels Jul 3, 2023

lorenrh closed this as completed Jul 3, 2023

solrevdev mentioned this issue Sep 18, 2023

Docker Desktop Warning - "Another application changed your Desktop configurations" has returned #6982

Closed

RogerWeihrauch mentioned this issue Mar 30, 2024

related to #6898: still not solved in my eyes #7230

Closed

seanbethard mentioned this issue Apr 16, 2024

Can't sign in to Docker Desktop #7160

Open

stevetoro mentioned this issue Apr 21, 2024

Docker doesn't start after 4.29 upgrade without installing Rosetta #7243

Closed

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

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

Comments

solrevdev commented Jun 30, 2023 • edited

Description

Reproduce

Expected behavior

docker version

docker info

Diagnostics ID

Additional Info

tksrc commented Jul 1, 2023

carrete commented Jul 2, 2023 • edited

bitbemol commented Jul 3, 2023

tkm5 commented Jul 3, 2023

sbrosgol commented Jul 3, 2023

dwzrlp commented Jul 3, 2023

lorenrh commented Jul 3, 2023

AnilG3 commented Sep 18, 2023

der-Lehmann commented Sep 18, 2023 • edited

solrevdev commented Sep 18, 2023 • edited

lorenrh commented Sep 18, 2023

solrevdev commented Sep 18, 2023

jamshid commented Sep 18, 2023

silverdr commented Sep 19, 2023

kcaashish commented Sep 20, 2023

wAuner commented Sep 27, 2023 • edited

bsousaa commented Sep 27, 2023

jaichinger commented Sep 28, 2023 • edited

jirsbek commented Oct 3, 2023 • edited

der-Lehmann commented Oct 3, 2023 • edited

ViggoV commented Oct 6, 2023

dielsonsales commented Mar 28, 2024 • edited

greenflute commented Mar 29, 2024 • edited

crmcmullen commented Mar 29, 2024

pankaj0825 commented Mar 30, 2024

edupmon commented Mar 31, 2024 • edited

SunnyVats0103 commented Apr 1, 2024

Steps I performed to resolve the issue:

josealbertomartinezvi commented Apr 1, 2024

zarfmouse commented Apr 2, 2024 • edited

zakariasassi commented Apr 3, 2024 • edited

panique commented Apr 4, 2024 • edited

fharper commented Apr 4, 2024

cyhsu commented Apr 5, 2024

c-ameron commented Apr 5, 2024

krzysztof-ziemacki commented Apr 6, 2024

seanbethard commented Apr 6, 2024

amadorssa commented Apr 8, 2024

petersg83 commented Apr 9, 2024 • edited

bsousaa commented Apr 9, 2024

julioromano commented Apr 9, 2024

tomson611 commented Apr 9, 2024

jvindel commented Apr 10, 2024

PeterCai7 commented Apr 11, 2024

lilian-miakito commented Apr 12, 2024 via email

Gruven commented Apr 25, 2024

napa3um commented May 1, 2024

ALFmachine commented May 9, 2024

EvanPoe commented May 16, 2024

solrevdev commented Jun 30, 2023 •

edited

carrete commented Jul 2, 2023 •

edited

der-Lehmann commented Sep 18, 2023 •

edited

solrevdev commented Sep 18, 2023 •

edited

wAuner commented Sep 27, 2023 •

edited

jaichinger commented Sep 28, 2023 •

edited

jirsbek commented Oct 3, 2023 •

edited

der-Lehmann commented Oct 3, 2023 •

edited

dielsonsales commented Mar 28, 2024 •

edited

greenflute commented Mar 29, 2024 •

edited

edupmon commented Mar 31, 2024 •

edited

zarfmouse commented Apr 2, 2024 •

edited

zakariasassi commented Apr 3, 2024 •

edited

panique commented Apr 4, 2024 •

edited

petersg83 commented Apr 9, 2024 •

edited