-
Notifications
You must be signed in to change notification settings - Fork 276
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
Cannot reenable podman extension, getting Extension error: command 'podman.onboarding.installWSL' already exists #4593
Comments
Same issue here, I'll just add some screensshots: The enable button in the overview section 'Extensions' seems to be missing. After clicking the enable button in detail of Podman extension, it gets stuck enabling, as @odockal said. |
@odockal I'm not reproducing this issue |
@benoitf Just right now I was able to reproduce. |
@benoitf Windows is expected platform. |
@benoitf I believe that we also need to install podman since |
Moreover, the disable-enable action introduces duplicated Podman resource objects in Resources. |
ok got it, specific to windows |
fixes containers#4593 Signed-off-by: Florent Benoit <fbenoit@redhat.com>
fixes #4593 Signed-off-by: Florent Benoit <fbenoit@redhat.com>
fixes containers#4593 Signed-off-by: Florent Benoit <fbenoit@redhat.com>
fixes #4593 Signed-off-by: Florent Benoit <fbenoit@redhat.com>
Bug description
I was facing a strange issue, after some time of playing around podman machines, pulling images, starting a containers, etc., I have seen a missing rootful, usermode, etc buttons in the create a new machine form. @lstocchi Also reported something similar.
I tried to disable and re-enable podman extension and got this:
Operating system
Windows 10 Professional
Installation Method
Installer from website/GitHub releases
Version
next (development version)
Steps to reproduce
Actual result: It gets stuck in enabling. Console shows an error. To get full error - force reload, aka. CTRL + R
Relevant log output
Additional context
Workaround - restart podman desktop (fully)
The text was updated successfully, but these errors were encountered: