Another application changed your Desktop configurations. #7109

mortonmj · 2023-12-10T20:19:57Z

Description

Docker: 4.26.0
macOS: 14.1.2

Fresh install and yet to be used Docker Desktop.

Deletion of the symlink /var/run/docker.sock --> /Users/username/.docker/run/docker.sock is occurring upon reboot of MacOS (Sonoma). This appears to be causing the error "Another application changed your Desktop configurations. This may cause unexpected behaviour and errors." with first start of Docker Desktop after a MacOS reboot. The content of the actual configuration file /Users/username/.docker/run/docker.sock is not lost. Just the symlink is being deleted.

If the symlink is created manually, after a MacOS reboot, and before starting Docker Desktop, the problem upon Docker Desktop start does not occur.

sudo ln -s /Users/username/.docker/run/docker.sock /var/run/docker.sock

Reproduce

Reboot MacOS
Start Docker Desktop

Expected behavior

No response

docker version

Client:
 Cloud integration: v1.0.35+desktop.5
 Version:           24.0.7
 API version:       1.43
 Go version:        go1.20.10
 Git commit:        afdd53b
 Built:             Thu Oct 26 09:04:20 2023
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.26.0 (130397)
 Engine:
  Version:          24.0.7
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.10
  Git commit:       311b9ff
  Built:            Thu Oct 26 09:08:15 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.25
  GitCommit:        d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f
 runc:
  Version:          1.1.10
  GitCommit:        v1.1.10-0-g18a0cb0
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

** Note: Actual user name replaced with token 'username' for privacy reasons.

Client:
 Version:    24.0.7
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.0-desktop.2
    Path:     /Users/username/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.23.3-desktop.2
    Path:     /Users/username/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/username/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.21
    Path:     /Users/username/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  0.1
    Path:     /Users/username/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.10
    Path:     /Users/username/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/username/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/username/.docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.2.0
    Path:     /Users/username/.docker/cli-plugins/docker-scout

Server:
 Containers: 35
  Running: 19
  Paused: 0
  Stopped: 16
 Images: 11
 Server Version: 24.0.7
 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: d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f
 runc version: v1.1.10-0-g18a0cb0
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.5.11-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 16
 Total Memory: 7.662GiB
 Name: docker-desktop
 ID: 1d92d2a9-3a21-4c21-a92c-851c928fbd62
 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

WARNING: daemon is not using the default seccomp profile

Diagnostics ID

f977a14c-36c0-402e-b1cf-c9a5b2846609/20231210200744

Additional Info

Problem was also previously reported in the following, which are now CLOSED without a resolve, but only a workaround. So opening again to request an actual fix.

#6898
#6982

mortonmj · 2023-12-19T14:11:49Z

Docker: 4.26.1
macOS: 14.2

Still not fixed.

alexkoepke · 2023-12-23T16:00:38Z

Docker: 4.26.1
macOS: 14.2.1

Still not fixed.

I will say that I tried the steps to workaround the issue and was unsuccessful.

Disable Docker start on boot.
Reboot macbook
Confirm that symlink was no present.

❯ ls -al /var/run/docker.sock
ls: /var/run/docker.sock: No such file or directory

Manually recreated symlink

 ❯ sudo ln -s /Users/alexkoepke/.docker/run/docker.sock /var/run/docker.sock
Password:
ln: /var/run/docker.sock: File exists
❯ ls -al /var/run/docker.sock
lrwxr-xr-x  1 root  daemon  46 Dec 23 10:58 /var/run/docker.sock -> /Users/alexkoepke/.docker/run/docker.sock

Started Docker Desktop
Still have the error, "Another application changed your Desktop configurations"

I will also confirm that when Docker Desktop is set to start on sign in that the symlink is present and that the error still persists.

mortonmj · 2023-12-24T22:25:56Z

Docker: 4.26.1
macOS: 14.2.1

Still not fixed.

LukaGiorgadze · 2024-01-09T09:21:55Z

Same Issue.

Apple M2
macOS: Sonoma 14.2.1 (23C71)
Docker: 4.26.1 (131620)

bencodesall · 2024-01-17T16:17:08Z

Same Issue

Apple M2 Max
macOS: Ventura 13.6.3
Docker Desktop: 4.25.2 (129061)
Engine: 24.0.6
Compose: v2.23.0-desktop.1
Credential Helper: v0.7.0
Kubernetes: v1.28.2
Docker Info:

Client:
 Version:    24.0.6
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     /Users/me/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.23.0-desktop.1
    Path:     /Users/me/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/me/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/me/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.9
    Path:     /Users/me/.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/me/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/me/.docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.9
    Path:     /Users/me/.docker/cli-plugins/docker-scout

Server:
 Containers: 5
  Running: 0
  Paused: 0
  Stopped: 5
 Images: 3
 Server Version: 24.0.6
 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: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.4.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 12
 Total Memory: 15.61GiB
 Name: linuxkit-6275e5017dfa
 ID: 8c75c7fc-e3a5-4664-b268-3327bd9dda39
 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

ugabiga · 2024-01-23T07:36:53Z

If you're using macOS Sonoma, installing Rosetta 2 could be beneficial. how to install rosetta 2

sigseg5 · 2024-01-25T07:47:37Z

Same on M1 Max with macOS Sonoma 14.3

Version: 4.26.1 (131620)
Engine: 24.0.7
Compose: v2.23.3-desktop.2
Credential Helper: v0.7.0
Kubernetes: v1.28.2

bencodesall · 2024-01-25T18:35:41Z

If you're using macOS Sonoma, installing Rosetta 2 could be beneficial. how to install rosetta 2

Already installed. Also, what specifically about Rosetta 2 are you trying to communicate by this comment?

mortonmj · 2024-01-26T18:44:12Z

Docker: 4.27.0
macOS: 14.3

Still not fixed.

enricodeleo · 2024-01-28T17:45:45Z

Same here :(

Mac mini M1
Docker: 4.26.1
Engine: 24.0.7
Compose: v2.23.3-desktop.2
Kubernetes: v1.28.2
MacOS: 14.3

HayoBaan · 2024-02-04T10:41:42Z

Same here

Mac Mini M2
Mac OS 14.2.1
Docker 4.27.1

Also: on startup I now always get the dashboard to open, even though the option is disabled. Very annoying.

mortonmj · 2024-02-09T21:52:31Z

Docker: 4.27.1 (136059)
macOS: 14.3.1

Still not fixed.

mscandan · 2024-02-12T13:42:23Z

Docker: 4.27.2 (137060)
macOS: 14.2.1 (23C71)

Still having the issue.

mortonmj · 2024-02-19T16:38:45Z

Docker: 4.27.2 (137060)
macOS: 14.3.1

Still not fixed.

bsousaa · 2024-02-20T12:38:13Z

can you share minimal steps to reproduce this issue? It is not clear to me why the deletion of /Users/username/.docker/run/docker.sock occurs.

Mhairi-Helen · 2024-02-21T11:12:57Z

Mac M1 Pro
macOS: 14.3.1
Docker: 4.27.2

On mac restart docker displays the following:
"Another application changed your Desktop configurations. This may cause unexpected behaviour and errors."

Still not fixed.

Leonid99 · 2024-02-21T15:19:11Z

It might be that only the version from homebrew is prone to this problem -- I am on an older version (4.27.1, due to docker/compose#11469) that I installed manually and I don't think this problem reproduces. It definitely did when I was using version 4.27.1 from homebrew.

nderambure · 2024-02-21T17:38:19Z

It might be that only the version from homebrew is prone to this problem -- I am on an older version (4.27.1, due to docker/compose#11469) that I installed manually and I don't think this problem reproduces. It definitely did when I was using version 4.27.1 from homebrew.

Nope, same from dmg install.

mortonmj · 2024-02-21T18:07:22Z

It might be that only the version from homebrew is prone to this problem -- I am on an older version (4.27.1, due to docker/compose#11469) that I installed manually and I don't think this problem reproduces. It definitely did when I was using version 4.27.1 from homebrew.

Nope, same from dmg install.

Same...DMG install.

mortonmj · 2024-02-21T23:59:56Z

can you share minimal steps to reproduce this issue? It is not clear to me why the deletion of /Users/username/.docker/run/docker.sock occurs.

Take a look at the information I provided upon opening this issue. In other referenced issues is where someone else figured out that in some cases that docker.sock is being deleted upon MacOS reboot. And then correlated this to the occurrence of the problem for which this issue is occuring. It is all we have to go by at the moment with what is causing this issue.

mattpackwood · 2024-02-24T15:06:42Z

So based on what @mortonmj said, if we assume that the issue is that docker.sock is being deleted at boot there are (I would suggest) two ways to address this:

Bug report to Apple to ask them to stop (unlikely to be successful in the short term)
Bug report to Docker asking them to stop checking for this (as I believe Docker recreates docker.sock on start up anyway)

Anyone know how to get ahold of Docker?

Matt

bsousaa · 2024-02-24T15:34:39Z

From Docker's side you can disable this check from Settings > Advanced > Automatically check configuration. Though I find it surprising that something is deleting docker.sock.

NiklasBr · 2024-02-27T14:31:00Z

I am getting this issue a lot today after upgrading to v4.28.0, no matter how many times I click Re-apply configurations it appears again after a few minutes.

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/nikbr/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.6-desktop.1
    Path:     /Users/nikbr/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.24
    Path:     /Users/nikbr/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/nikbr/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.22
    Path:     /Users/nikbr/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /Users/nikbr/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.0.1
    Path:     /Users/nikbr/.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/nikbr/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.5.0
    Path:     /Users/nikbr/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/nikbr/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/nikbr/.docker/cli-plugins/docker-scan: no such file or directory

Server:
 Containers: 44
  Running: 11
  Paused: 0
  Stopped: 33
 Images: 46
 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: 9
 Total Memory: 23.44GiB
 Name: docker-desktop
 ID: 4bacd5ea-52d7-4544-a700-b29136ca8a38
 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

WARNING: daemon is not using the default seccomp profile

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

BMeach · 2024-03-19T03:56:26Z

This fixed it for me: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

Thank you, this fixed it for me!

MacBook Pro M3 Max 2023
macOS Sonoma 14.4 (23E214)
Docker Desktop 4.28.0 (139021)

user-ShDVR · 2024-03-20T16:31:02Z

This fixed it for me: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

M1 MacBook Pro Sonoma Version 14.3 (23D56) Docker 4.28.0 (139021)

Thank you, this fixed it for me!
Macbook Pro M1 2020
macOS Sonoma 14.4
Docker Desktop 4.28.0 (139021)

menlazar · 2024-03-21T00:00:11Z

This fixed it for me: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

M1 MacBook Pro Sonoma Version 14.3 (23D56) Docker 4.28.0 (139021)

it worked perfectly, many thanks!
Macbook Pro i9 2019
MacOS Sonoma 14.4
Docker Desktop 4.28.0 (139021)

Bandito11 · 2024-03-23T19:10:42Z

Docker version 25.0.3, MacBook Pro M3 Max 2023, Sonoma v 14.3

sudo

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

worked for me thanks!

This also worked for me! Thanks.
On Sonoma 14.4, Macbook Air M1. Docker Desktop 4.28

dauden · 2024-03-24T02:55:22Z

If you are using
Choose how to configure the installation of Docker's CLI tools: User

ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login $HOME/.docker/bin/docker-credential-ecr-login

On Sonoma 14.0, iMac Pro (Mac Intel) Docker Desktop 4.28.0 (139021)

michaelubembe · 2024-03-26T19:09:29Z

This fixed it for me: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

M1 MacBook Pro Sonoma Version 14.3 (23D56) Docker 4.28.0 (139021)

This fixed for me. Thank you so much. M2 Macbook Air Sonoma 14.4

franklin-conza-tech-ec · 2024-03-27T20:46:28Z

eres un crack!!!

fabriziobagala · 2024-04-01T09:39:35Z

I too had the same tedious problem and solved it by typing from the terminal:
sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

MacBook Pro M2 Max
macOS Sonoma 14.4.1
Docker Desktop 4.28.0 (139021)

zkdiff · 2024-04-08T14:43:13Z

This might be of interest: https://docs.docker.com/desktop/mac/permission-requirements/#installing-symlinks

Seems like this behaviour is documented I guess. I have a collision from running multiple instances in parallel which is what led me to find this doc. My approach is going to be to just not use the default socket location and hopefully that will resolve this. But it seems worth checking into launchd and permissions.

Ryearwood · 2024-04-10T16:21:10Z

This fixed it for me: ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

M1 MacBook Pro Sonoma Version 14.3 (23D56) Docker 4.28.0 (139021)

This fixed it for me, though I used sudo instead
sudo ln -sf /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login /usr/local/bin/docker-credential-ecr-login

Kallepan · 2024-04-18T10:04:47Z

Docker Desktop version 4.29.0 (145265) seems to have fixed it for me.

Maybe related to this fix:
Fixed a bug when the browser was not able to send back authentication information to Docker Desktop. Fixes docker/for-mac/issues#7160?

MacBook Pro M3 Pro
macOS Sonoma 14.4.1

flaxpanda · 2024-05-07T00:57:03Z

docker desktop version 4.29.0 (145265) did NOT fix the issue for me. every time i restart my machine docker warns that another app has changed my settings...

i see 4 items where docker wants to run automatically behind the scenes on login which i have purposefully disabled. i wonder if this issue could be due to the fact i have disabled auto start docker in the login items settings screens?

Apple M1 Max
Mac OS 14.4.1

ldemailly · 2024-07-03T00:23:25Z

4.31.0 and getting this issue on macOS 14.5 (23F79)

NiklasBr · 2024-07-05T07:18:21Z

4.32.0 and this annoyance is still here.

NiklasBr · 2024-07-11T15:33:50Z

Hope I can get the bot to tag the current version:

docker info

Client:
 Version:    27.0.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.15.1-desktop.1
    Path:     /Users/nikbr/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.28.1-desktop.1
    Path:     /Users/nikbr/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.32
    Path:     /Users/nikbr/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     /Users/nikbr/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/nikbr/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     /Users/nikbr/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/nikbr/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/nikbr/.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/nikbr/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.10.0
    Path:     /Users/nikbr/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/nikbr/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/nikbr/.docker/cli-plugins/docker-scan: no such file or directory

Server:
 Containers: 27
  Running: 12
  Paused: 0
  Stopped: 15
 Images: 54
 Server Version: 27.0.3
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 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: ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.6.32-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 9
 Total Memory: 23.44GiB
 Name: docker-desktop
 ID: 4bacd5ea-52d7-4544-a700-b29136ca8a38
 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
 Labels:
  com.docker.desktop.address=unix:///Users/nikbr/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

docker version

Client:
 Version:           27.0.3
 API version:       1.46
 Go version:        go1.21.11
 Git commit:        7d4bcd8
 Built:             Fri Jun 28 23:59:41 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.32.0 (157355)
 Engine:
  Version:          27.0.3
  API version:      1.46 (minimum version 1.24)
  Go version:       go1.21.11
  Git commit:       662f78c
  Built:            Sat Jun 29 00:02:44 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.18
  GitCommit:        ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
 runc:
  Version:          1.7.18
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

jdeepwell · 2024-07-22T06:11:28Z

4.32.0 and macOS 14.5 (23F79) – still seeing this issue. As the advanced setting to temporarily disable the check is gone I am rapidly getting used to ignoring this (presumably normally important) message 😔

NiklasBr · 2024-08-05T08:57:29Z

Because this has not been fixed in v4.33.0…

Client:
 Version:           27.1.1
 API version:       1.46
 Go version:        go1.21.12
 Git commit:        6312585
 Built:             Tue Jul 23 19:54:12 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.33.0 (160616)
 Engine:
  Version:          27.1.1
  API version:      1.46 (minimum version 1.24)
  Go version:       go1.21.12
  Git commit:       cc13f95
  Built:            Tue Jul 23 19:57:14 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.19
  GitCommit:        2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
 runc:
  Version:          1.7.19
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Client:
 Version:    27.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1-desktop.1
    Path:     /Users/nikbr/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.1-desktop.1
    Path:     /Users/nikbr/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     /Users/nikbr/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     /Users/nikbr/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/nikbr/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     /Users/nikbr/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/nikbr/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/nikbr/.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/nikbr/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.11.0
    Path:     /Users/nikbr/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/nikbr/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/nikbr/.docker/cli-plugins/docker-scan: no such file or directory

Server:
 Containers: 27
  Running: 0
  Paused: 0
  Stopped: 27
 Images: 54
 Server Version: 27.1.1
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 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: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.10.0-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 9
 Total Memory: 23.44GiB
 Name: docker-desktop
 ID: 4bacd5ea-52d7-4544-a700-b29136ca8a38
 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
 Labels:
  com.docker.desktop.address=unix:///Users/nikbr/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

bsousaa · 2024-08-06T14:57:57Z

@NiklasBr can you describe the exact problem you are facing with 4.33? Please share a diagnostics id. As this thread is getting long I suggest you open a new issue.

NiklasBr · 2024-08-06T15:04:00Z

@bsousaa why should I create a duplicate issue for the error "Another application changed your Desktop configurations" when my issue is exactly the same as originally posted?

bsousaa · 2024-08-06T15:29:56Z

@NiklasBr the original issue was reported with 4.26. Since then we did multiple changes to the Configuration integrity check. See https://www.docker.com/blog/docker-desktop-4-33/#configuration

If you are still facing the issue with the latest, we would appreciate an exact description with steps about how to reproduce and respective diagnostic id.

NiklasBr · 2024-08-06T19:17:48Z

@bsousaa please don't take this as an odd or p-a response, but the exact description with steps you ask for are just at the top of this very thread, so for your convenience I am now quoting them pretty much verbatim:

Description

Docker: all versions from 4.26.0 to current 4.33.0 macOS: all versions from 14.1.2 to 14.6.0

Fresh install and yet to be used Docker Desktop.

Deletion of the symlink /var/run/docker.sock --> /Users/username/.docker/run/docker.sock is occurring upon reboot of MacOS (Sonoma). This appears to be causing the error "Another application changed your Desktop configurations. This may cause unexpected behaviour and errors." with first start of Docker Desktop after a MacOS reboot. The content of the actual configuration file /Users/username/.docker/run/docker.sock is not lost. Just the symlink is being deleted.

If the symlink is created manually, after a MacOS reboot, and before starting Docker Desktop, the problem upon Docker Desktop start does not occur.

sudo ln -s /Users/username/.docker/run/docker.sock /var/run/docker.sock

Reproduce
1. Reboot MacOS

2. Start Docker Desktop
Additional Info

Problem was also previously reported in the following, which are now CLOSED without a resolve, but only a workaround. So opening again to request an actual fix.

#6898 #6982

bsousaa · 2024-08-06T19:24:48Z

thanks @NiklasBr. Can you add a Diagnostics Id?

NiklasBr · 2024-08-09T07:58:09Z

I installed Mac OS 14.6.1 (23G93) and rebooted yesterday, when I started Docker Desktop this morning I got the error message again.

Diagnostics ID: 39263439-8ED3-425A-A6C1-A4B1DD929F05/20240809075535

jdeepwell · 2024-08-09T08:14:13Z

@NiklasBr Could you share a screenshot of the panel displayed when you click on "Find out more"?

NiklasBr · 2024-08-09T08:24:01Z

jdeepwell · 2024-08-10T16:28:00Z

Thx. Have you in the past clicked the "Repair" button?

My experience: I had the "Another application changed..." message again after updating to Docker Desktop 4.33.0 (macOS 14.5, 23F79) – and that symlink (plus another one) really was wrong - so I clicked the repair button (again - did that in past versions also). Now the symlink points to /Applications/Docker.app/Contents/Resources/cli-plugins/docker-compose (where docker-compose actually is) and since then (after restarting Docker Desktop several times and also rebooting) no issues anymore.

My assumption: In past versions of Docker Desktop the "Repair" button did not really alter the wrong symlinks the right way – hence the re-appearing error message. Now it seams to really correct the symlinks...(🤞)

J.

NiklasBr · 2024-08-15T07:06:43Z

I have clicked it so many times by now…

jdeepwell · 2024-08-15T07:15:48Z

And after clicking it, does the symlink still point to the wrong ...Resources/bin/... instead of the correct .../Resources/cli-plugins/... or was it corrected?

I'm just asking to find out whether the Repair button actually does correct the symlink but it later get's reversed somehow (e.g. by updating Docker Desktop or by an OS update etc.) or whether it just doesn't do what it is supposed to in the first place.

mortonmj added the needs-triage label Dec 10, 2023

docker-robot bot added the version/4.26.0 label Dec 10, 2023

bsousaa added status/triage area/gui and removed needs-triage labels Dec 12, 2023

HayoBaan mentioned this issue Feb 4, 2024

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

Closed

docker-robot bot added the version/4.28.0 label Feb 27, 2024

docker-robot bot added the version/4.32.0 label Jul 11, 2024

docker-robot bot added the version/4.33.0 label Aug 5, 2024

Another application changed your Desktop configurations. #7109

Another application changed your Desktop configurations. #7109

Comments

mortonmj commented Dec 10, 2023

Description

Reproduce

Expected behavior

docker version

docker info

Diagnostics ID

Additional Info

mortonmj commented Dec 19, 2023

alexkoepke commented Dec 23, 2023 • edited Loading

mortonmj commented Dec 24, 2023

LukaGiorgadze commented Jan 9, 2024

bencodesall commented Jan 17, 2024

ugabiga commented Jan 23, 2024 • edited Loading

sigseg5 commented Jan 25, 2024

bencodesall commented Jan 25, 2024

mortonmj commented Jan 26, 2024

enricodeleo commented Jan 28, 2024

HayoBaan commented Feb 4, 2024

mortonmj commented Feb 9, 2024

mscandan commented Feb 12, 2024

mortonmj commented Feb 19, 2024

bsousaa commented Feb 20, 2024

Mhairi-Helen commented Feb 21, 2024

Leonid99 commented Feb 21, 2024

nderambure commented Feb 21, 2024

mortonmj commented Feb 21, 2024

mortonmj commented Feb 21, 2024

mattpackwood commented Feb 24, 2024

bsousaa commented Feb 24, 2024

NiklasBr commented Feb 27, 2024

BMeach commented Mar 19, 2024

user-ShDVR commented Mar 20, 2024

menlazar commented Mar 21, 2024

Bandito11 commented Mar 23, 2024

dauden commented Mar 24, 2024

michaelubembe commented Mar 26, 2024 • edited Loading

franklin-conza-tech-ec commented Mar 27, 2024

fabriziobagala commented Apr 1, 2024 • edited Loading

zkdiff commented Apr 8, 2024

Ryearwood commented Apr 10, 2024

Kallepan commented Apr 18, 2024 • edited Loading

flaxpanda commented May 7, 2024 • edited Loading

ldemailly commented Jul 3, 2024

NiklasBr commented Jul 5, 2024

NiklasBr commented Jul 11, 2024

jdeepwell commented Jul 22, 2024

NiklasBr commented Aug 5, 2024

bsousaa commented Aug 6, 2024

NiklasBr commented Aug 6, 2024

bsousaa commented Aug 6, 2024

NiklasBr commented Aug 6, 2024

Description

Reproduce

Additional Info

bsousaa commented Aug 6, 2024

NiklasBr commented Aug 9, 2024

jdeepwell commented Aug 9, 2024

NiklasBr commented Aug 9, 2024

jdeepwell commented Aug 10, 2024 • edited Loading

NiklasBr commented Aug 15, 2024

jdeepwell commented Aug 15, 2024

alexkoepke commented Dec 23, 2023 •

edited

Loading

ugabiga commented Jan 23, 2024 •

edited

Loading

michaelubembe commented Mar 26, 2024 •

edited

Loading

fabriziobagala commented Apr 1, 2024 •

edited

Loading

Kallepan commented Apr 18, 2024 •

edited

Loading

flaxpanda commented May 7, 2024 •

edited

Loading

jdeepwell commented Aug 10, 2024 •

edited

Loading