Skip to content
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

Settings version is too high for the application #4537

Closed
2 tasks done
toreonify opened this issue May 9, 2020 · 3 comments
Closed
2 tasks done

Settings version is too high for the application #4537

toreonify opened this issue May 9, 2020 · 3 comments

Comments

@toreonify
Copy link

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: ACE68B7C-5E16-4F80-A0B9-5D152AE3B28A/20200509192237

What happened

Launching Docker with a few containers consumed almost all 8 GB of RAM, vpnkit-bridge consumed 3 GB of RAM. I've searched for the solution and found that I can try an latest Edge version of Docker Desktop.

Downloaded and it said that I cannot continue unless Docker deletes all configuration and data. Closed the message and downloaded version 2.2.0.5 that I had previously. After installing it, message saying "Settings version is too high for the application" appeared.

Error message

Information

  • macOS Version: 10.14.6
  • Docker Desktop 2.2.0.5

Steps to reproduce the behavior

  1. Install Docker Desktop 2.2.0.5
  2. Install over an Edge version 2.3.0.1
  3. Do not reset Docker configuration in popup window, so it closes and doesn't launch and delete containers
  4. Install 2.2.0.5 again
  5. Can't launch Docker because of setting file incompatibility
@toreonify
Copy link
Author

So, I was able to manually edit ~/Library/Group Containers/group.com.docker/settings.json and change settingsVersion from 6 back to 5 and Docker was able to start and no data was lost.

But still, I've not started 2.3.0.1 reset to defaults process, so why would it change settings so early?

@docker-robott
Copy link
Collaborator

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Oct 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants