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

Provide a "Reset Containers/Image" button #1309

Closed
errordeveloper opened this issue Feb 16, 2017 · 7 comments
Closed

Provide a "Reset Containers/Image" button #1309

errordeveloper opened this issue Feb 16, 2017 · 7 comments

Comments

@errordeveloper
Copy link

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.

@justincormack
Copy link
Member

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...

@dave-tucker
Copy link
Contributor

@errordeveloper based on @justincormack's comments I'm tempted to close as a wontfix.
Resetting in anger sucks - we know that - but what we want to do is to make it so you don't need to do it so often. A "Reset image/container storage" button might be the happy middle ground but I'll wait to hear from you to see what you think.

@errordeveloper
Copy link
Author

errordeveloper commented Feb 17, 2017

eg you could just delete the qcow file to remove all Docker state without affecting host state...

Ah, ok, that'll do 👍

Thanks @justincormack and @dave-tucker :)

@errordeveloper
Copy link
Author

A "Reset image/container storage" button might be the happy middle ground but I'll wait to hear from you to see what you think.

I think it'd be great to have this button.

@dave-tucker dave-tucker changed the title Would be very nice to keep memory and CPU settings on reset Provide a "Reset Containers/Image" button Feb 17, 2017
@dave-tucker
Copy link
Contributor

Ok, it's now on the internal tracker tagged for attention from the UI team.
We'll post back here when we have an update!

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d 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 Jun 22, 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

5 participants