You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got Java script uncaught exception when starting podman desktop 0.13.0 (or when binary is built from main branch - 0.14.0-next version) on linux when there is no podman installed on the system:
After I click OK, app is spawn eventually.
Operating system
Fedora 37
Version
0.13.0
Steps to reproduce
Download tarball for linux
extract
run
ASSERT: app is started properly
Actual result: error dialog is shown first
Relevant log output
No response
Additional context
The same can be reproduced when podman-desktop is built locally from main branch (0.14.0-next) and run.
Since I had podman installed for some time before, I decided to experiment with its removal, not sure that process was correct, I followed this guide here. Cannot exclude some system misconfiguration.
The text was updated successfully, but these errors were encountered:
odockal
changed the title
Error: spawn podman ENOENT when running PD 0.13.0 from released tarball on linux where is no podman installed
Error: spawn podman ENOENT when running PD 0.13.0 from released tarball on linux without podman
Mar 31, 2023
Bug description
I got Java script uncaught exception when starting podman desktop 0.13.0 (or when binary is built from main branch - 0.14.0-next version) on linux when there is no podman installed on the system:
After I click OK, app is spawn eventually.
Operating system
Fedora 37
Version
0.13.0
Steps to reproduce
Actual result: error dialog is shown first
Relevant log output
No response
Additional context
The same can be reproduced when podman-desktop is built locally from main branch (0.14.0-next) and run.
Since I had podman installed for some time before, I decided to experiment with its removal, not sure that process was correct, I followed this guide here. Cannot exclude some system misconfiguration.
The text was updated successfully, but these errors were encountered: