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.

[tksrc]

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]

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]

Same issue

[tkm5]

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]

same here, very annoying... :-(

[dwzrlp]

me too

[lorenrh]

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]

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

[der-Lehmann]

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]

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

[lorenrh]

Hello

The check can be disabled in Advanced Settings

[solrevdev]

Hello

The check can be disabled in Advanced Settings

Brilliant thank you @lorenrh

[jamshid]

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]

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]

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]

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]

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

[jaichinger]

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]

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 https://github.com/docker/for-mac/issues/6898#issuecomment-1723208892.

[der-Lehmann]

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]

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.

[tangix]

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.

Just chiming in here - this just happened to me after reboot after update to Docker 4.24.0

[huyz]

Is that all it means? that the /var/run/docker.sock was taken over by another app (e.g. Rancher Desktop or Podman Desktop)

[jbosse]

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.

I'm glad I now know the cause of the warning. I thought maybe a VSCode plugin was changing a config and the two applications were stepping on each other. Now that I know what is happening I guess I'm glad there is a warning. I'm looking forward to a resolution of preventing the file deletion in the first place.

[mortonmj]

Docker: 4.25.1 macOS: 14.1.1

Anyone have any idea why this issue is still not resolved?

[EM-Savard]

I have encountered the same issue. Providing a bit of context, I experimented Podman and Podman Desktop on my Mac, but ultimately reverted to using Docker Desktop again. However, now I am consistently encountering an error in the UI every time I open it....

🐳 Docker : 4.25.2 🍎 macOS: 13.6

[huyz]

@EM-Savard OOC, why are you going back to Docker Desktop? I'm actually thinking of going the other direction cause of issues.

[placeposition]

Me too after Mac update to 14.1.1, I cant run my php app.

MacOs 14.1.1 Docker Destop Version 4.25.2 (129061)

[mortonmj]

Docker: 4.25.2 macOS: 14.1.1

@tangix already posted why this is happening. It is literally a deletion of the symlink /var/run/docker.sock --> /Users/username/.docker/run/docker.sock when you reboot macos. So the content of the actual configuration file /Users/username/.docker/run/docker.sock is not lost. This issue was opened in June for this very solvable problem and it is still not fixed and CLOSED. 👎

[andrewgazelka]

Is there any way to debug this issue? I have tried deleting all docker-related files I could find on my MBP with find and re-installing Docker desktop, but I still get it 🥲

[factorial]

I ran into this issue today after allowing Microsoft's Auto-updater to install Microsoft Defender on my Mac, which comes with Microsoft Office 365. This is only a hunch, but in my case I suspect MS Defender is the app that changed Docker settings.

[NathanDotTo]

In my case, this was resolved without me having to provide my admin credentials. The warning went away whilst I was reading this issue.

[clemsau]

Issue is happening to me on a fresh install on a Mac.

Here are the steps I executed that led me to the issue:

• Downloaded the Docker.dmg file for Applie Silicon on the official page https://docs.docker.com/desktop/install/mac-install/
• In the terminal, I exectued the three commands provided on the same page to install docker in the command line
• Opened docker desktop that was then available through the launchpad
• It then led me to proceed to the standard process of accepting the TOS and signing in

I can now use docker from the CLI when docker desktop is on. But when I quit Docker desktop, if I run a docker command in the terminal, it will obviously won't work. But it seems like it changes the configurations.

It is pretty annoying, because in this case, even if Docker Desktop is running, I cannot run any docker command without re-applying the configuration, it simply doesn't work. Which constraint me to prompt my password.

[stonerl]

One action that is causing this is signing to one's docker hub account. As soon as is signed in, the error appeared for me. But also restarting the application without being signed in triggers this error.

[trevordcampbell]

@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?

[arriellie]

@trevordcampbell that worked for me, thank you!

I just toggled the setting off, launched docker desktop, re-applied, then toggled the setting back on. No more prompt!

[lilian-miakito]

It surprisingly worked here too. Gotta get back in a few days to see if it stays this way but thanks alot @trevordcampbell !

[nderambure]

I'm on MacOS 14.3, Docker Desktop 4.26.1 and the @trevordcampbell solution is not working anymore... Why is this issue still closed ?

[HayoBaan]

See “new” issue #7109

[krishnaTORQUE]

Hi

I am having the same issue. Docker Desktop v4.28.0 (139021) Mac: Sonoma 14.3.1

Please help, thanks.

[OktarinTentakel]

Same here, exactly the same versions as @krishnaTORQUE. Edit: I'm on a system with multiple users

[jpcercal]

It is also affecting me, and it's very annoying. I just did a fresh installation of macOS Sonoma 14.3.1 (23D60) running on Docker version 25.0.3, build 4debf41, Docker Desktop Version 4.28.0 (139021).

[dalisoft]

Same issue

---

docker info

Client:
 Version:    25.0.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1-desktop.4
    Path:     /Users/dalisoft/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.6-desktop.1
    Path:     /Users/dalisoft/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.24
    Path:     /Users/dalisoft/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/dalisoft/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.22
    Path:     /Users/dalisoft/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /Users/dalisoft/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.0.1
    Path:     /Users/dalisoft/.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/dalisoft/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.5.0
    Path:     /Users/dalisoft/.docker/cli-plugins/docker-scout

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 1
 Server Version: 25.0.3
 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 splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.6.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 2
 Total Memory: 2.85GiB
 Name: docker-desktop
 ID: b30806dd-9c67-4218-95d5-fe07ee6379ad
 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

---

docker version

Client:
 Cloud integration: v1.0.35+desktop.11
 Version:           25.0.3
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        4debf41
 Built:             Tue Feb  6 21:13:26 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.28.0 (139021)
 Engine:
  Version:          25.0.3
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       f417435
  Built:            Tue Feb  6 21:14:22 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Originally posted by @dalisoft in https://github.com/docker/for-mac/issues/7109#issuecomment-1977792620

[OktarinTentakel]

The logs tell me: localhost com.docker.backend[761]: configuration integrity - binary symlinks may be missing from /usr/local/bin or were changed by external tools

Looks alright to me though:

[Memnoch-The-Red]

Same issue.

[millievn]

Same issue

[ryankert01]

same issue

[ghost]

same issue ![Uploading iShot_2024-03-12_14.36.29.png…]()

[yuowo39]

I have the same issue.

Software Versions

• macOS 14.4 (23E214)
• Docker Desktop 4.28.0 (139021)

[bsousaa]

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