-
Notifications
You must be signed in to change notification settings - Fork 118
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
Provide a "Reset Containers/Image" button #1309
Comments
Part of the point of reset is total reset though; it is hard to tell what is "safe". What are you trying to reset in anger? eg you could just delete the qcow file to remove all Docker state without affecting host state... |
@errordeveloper based on @justincormack's comments I'm tempted to close as a |
Ah, ok, that'll do 👍 Thanks @justincormack and @dave-tucker :) |
I think it'd be great to have this button. |
Ok, it's now on the internal tracker tagged for attention from the UI team. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an 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. |
Closed issues are locked after 30 days of inactivity. 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. |
Expected behavior
Memory and CPU settings persisted on reset.
Actual behavior
Memory and CPU settings are reset and it take another restart to change these, easy to forget when resetting in anger.
The text was updated successfully, but these errors were encountered: