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
Are you targeting a kubernetes or an Openshift cluster ? If possible, provide its version: Openshift 4.13.4
What did you run exactly?
Start dev on podman on a created component
Actual behavior
Error saying /Users/lgrossma/.odo/cache/3.15.0/odo-darwin-amd64 dev --forward-localhost --platform podman --debug ✗ unable to access podman. Do you have podman client installed and configured correctly? cause: exec: "podman": executable file not found in $PATH
Expected behavior
The dev is started on podman
Any logs, error output, etc?
I tried the same scenario with the vscode extension successfully. I tried it on the same created component and the odo versions are also the same, altough I am not sure if the same odo binary is used in both cases. This might also be the culprit as the vscode extension odo binary might have different rights and thus can see podman on the path? (just an idea...)
The text was updated successfully, but these errors were encountered:
What versions of software are you using?
What did you run exactly?
Start dev on podman on a created component
Actual behavior
Error saying
/Users/lgrossma/.odo/cache/3.15.0/odo-darwin-amd64 dev --forward-localhost --platform podman --debug ✗ unable to access podman. Do you have podman client installed and configured correctly? cause: exec: "podman": executable file not found in $PATH
Expected behavior
The dev is started on podman
Any logs, error output, etc?
I tried the same scenario with the vscode extension successfully. I tried it on the same created component and the odo versions are also the same, altough I am not sure if the same odo binary is used in both cases. This might also be the culprit as the vscode extension odo binary might have different rights and thus can see podman on the path? (just an idea...)
The text was updated successfully, but these errors were encountered: