-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another application changed your Desktop configurations. #7109
Comments
Docker: 4.26.1 Still not fixed. |
Docker: 4.26.1 I will say that I tried the steps to workaround the issue and was unsuccessful.
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. |
Docker: 4.26.1 Still not fixed. |
Same Issue. Apple M2 |
Same Issue Apple M2 Max
|
If you're using macOS Sonoma, installing Rosetta 2 could be beneficial. how to install rosetta 2 |
Same on M1 Max with macOS Sonoma 14.3 Version: 4.26.1 (131620) |
Already installed. Also, what specifically about Rosetta 2 are you trying to communicate by this comment? |
Docker: 4.27.0 Still not fixed. |
Same here :( Mac mini M1 |
Same here Mac Mini M2 Also: on startup I now always get the dashboard to open, even though the option is disabled. Very annoying. |
Docker: 4.27.1 (136059) Still not fixed. |
Docker: 4.27.2 (137060) Still having the issue. |
Docker: 4.27.2 (137060) Still not fixed. |
can you share minimal steps to reproduce this issue? It is not clear to me why the deletion of |
Mac M1 Pro On mac restart docker displays the following: Still not fixed. |
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. |
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. |
So based on what @mortonmj said, if we assume that the issue is that
Anyone know how to get ahold of Docker? Matt |
From Docker's side you can disable this check from Settings > Advanced > Automatically check configuration. Though I find it surprising that something is deleting |
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.
|
Thank you, this fixed it for me! MacBook Pro M3 Max 2023 |
Thank you, this fixed it for me! |
it worked perfectly, many thanks! |
This also worked for me! Thanks. |
This fixed for me. Thank you so much. M2 Macbook Air Sonoma 14.4 |
eres un crack!!! |
I too had the same tedious problem and solved it by typing from the terminal: MacBook Pro M2 Max |
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. |
This fixed it for me, though I used sudo instead |
Docker Desktop version 4.29.0 (145265) seems to have fixed it for me. Maybe related to this fix: MacBook Pro M3 Pro |
4.31.0 and getting this issue on macOS 14.5 (23F79) |
Hope I can get the bot to tag the current version:
|
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 😔 |
Because this has not been fixed in v4.33.0…
|
@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. |
@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? |
@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. |
@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:
|
thanks @NiklasBr. Can you add a Diagnostics Id? |
@NiklasBr Could you share a screenshot of the panel displayed when you click on "Find out more"? |
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 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. |
I have clicked it so many times by now… |
And after clicking it, does the symlink still point to the wrong 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. |
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
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
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
The text was updated successfully, but these errors were encountered: