-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
RFE: Expose system reset
to the API / remote CLI
#15886
Comments
Is this a good idea? I feel like allowing users to reset settings from another machine via an API (think in non podman-machine scenarios) feels dangerous. I'd much rather have podman machine do a |
That makes sense to me. We are not allowing most/all podman system * objects to be manipulated via a remote API. |
The request from the desktop team was a way to "factory reset" a VM that is having problems. In that context, it seems reasonable to expose some way to do this - unless we want to require something like |
I'd be okay with something like a podman machine reset command, but that would literally just be a wrapper around |
what does factory reset mean? the contents of the vm are reset or the vm itself is reset? |
From a 'Client' point of view, after the reset, everything should work again and it includes data loss. It may include a podman reset or a vm reset as well. (Sometimes podman machine is not starting anymore so podman machine ssh will hang as well as the machine is not responding) so it may be: |
It might be safer to destroy the VM and recreate it rather then just reset the container storage. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
Sometimes, podman machine is not working as expected. One example is #15526
But to call
podman system reset
we need first to ssh into the machine which is not so convenient for users.Steps to reproduce the issue:
podman machine ssh
podman system reset
Describe the results you received:
2 steps
Describe the results you expected:
Add a REST API to call the reset command.
It will allow tools like Podman Desktop to add a
reset machine
optionin addition a
podman machine reset
would help end users.Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes/No
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: