Rootful podman machine gets stuck using rootless connection if previously there was a rootless podman machine set as default #22577
Assignees
Labels
jira
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
machine
Comments
|
Additional note, I was also able to reproduce this on macOS. |
|
I can reproduce this on linux as well. Taking a look |
|
/assign |
|
I think this is already being fixed in #22587 |
Sorry nevermind, wrong issue |
jakecorrenti
added a commit
to jakecorrenti/podman
that referenced
this issue
Sep 12, 2024
When a machine is removed, it removes the current system connection and will select a new one from the top of the alphabetical list. However, when doing this there is no guarantee that, if the new system connection is associated with a machine, the new system connection will have the right rootfulness. This will ensure that the new connection, if associated with a machine, will have proper rootfulness. Fixes: containers#22577 Signed-off-by: Jake Correnti <jakecorrenti+github@proton.me>
stale-locking-app
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Description
If the user has two podman machines running at the same time on WSL, one fo them rootful and the other rootless, with the rootless one being set as default, if the user deletes the rootless machine the rootful podman machine will become default, however it's rootless connection will be used, not the rootful one.
Steps to reproduce the issue
Steps to reproduce the issue
podman system connection listand notice that the rootless connection of the remaining rootful podman machine is now default.Describe the results you received
Rootful podman machine will only using the rootless connection going forward, stopping and starting the machine does not help.
Describe the results you expected
the rootful connection of the rootful podman machine should become default.
podman info output
If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Issue is only reproducible on Windows operating system.
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: