-
Notifications
You must be signed in to change notification settings - Fork 274
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
Rootful podman machine gets stuck using rootless connection after another rootless machine is deleted #7052
Comments
when you say 'get stuck' it's all about the CLI ? |
@benoitf most of it is CLI yes, but the fact that the popup in PD no longer gets triggered is a PD issue. |
but Podman Desktop should not be a tool to workaround podman CLI bugs maybe it's another one like containers/podman#16483 in the past |
@benoitf @odockal created containers/podman#22577 in the podman repo |
I wouldn't describe PD's functionality of displaying a popup as a workaround, especially since it's broken until the app is restarted. For example even if the user deletes all the podman machines and creates new ones, and as such everything is perfectly ok with the podman connections, the PD popup that notifies the user about default podman machines will still not be displayed. A full app restart will be required. |
Was also able to reproduce this on macOS in PD 1.10.2 |
Still present in 1.10.3 |
Bug description
It seems that in some situations a rootful podman machine can get stuck using a rootless connection if the user deletes another podman machine which is rootless and is set to default at the same time.
Additionally it seems that this scenario also makes the "This machine is not set to default" prompt to be displayed at all until such time that the user manually shuts down Podman Desktop and reopens it.
Operating system
Windows 11
Installation Method
Installer from website/GitHub releases
Version
1.10.0
Steps to reproduce
Ignore
option on the popup.podman system connection list
will display the rootful podman machines's connections, but will show that the rootless connection is the one set to default, not the rootful one as it should be.Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: