podman installed but propose to install podman

[jeffmaury]

I have podman installed on my machine and wanted to start a component. I got:

I don't know if this is related but I have podman installed but no podman machine are defined on my system (Win11Pro)

[datho7561]

We are using odo to check if podman is present. As such, this might be an upstream issue with odo. What does the output of odo version give? I'll try it out on my Windows computer as well.

If this feature of odo isn't working reliably on Windows, we can look into using the which library to search the path for the podman binary.

[jeffmaury]

I have a very old version of odo in the PATH (3.4.0)

[jeffmaury]

But removing this old version from the PATH did not change the behavoir. And I don't know where is located odo binary used by the extension

[jeffmaury]

OK found the odo binary in the $HOME/.vscode/extensions folder hierarchy.

So running odo-windows-amd64 dev --platform podman

gives:

X unable to access podman. Do you have podman client installed and configured correctly? cause: exit status 125

And having a podman machine running fixes the issue.

And having a podman machine but stopped gives the following output:

X unable to access podman. Do you have podman client installed and configured correctly? cause: timeout (1s) while waiting for Podman version

[datho7561]

What does odo version report? This is what we are using to tell if podman is installed on the user's system. If that part of odo is broken, we will migrate off of it, since we already require a library that can tell if a given program is on the PATH.

As a side note, I tend to run into a lot of problems trying to use podman on Windows, I don't know if that's related.

[jeffmaury]

Once I removed my old odo version from PATH, so I had no odo in the PATH and I had to add the one in $HOME/.vscode/extensions/xxxx and it reported:

 !  unable to fetch the cluster server version
odo v3.14.0 (471928fea)

Podman Client: 4.6.2

---
A newer version of odo (v3.15.0) is available,
visit https://github.com/redhat-developer/odo/releases to update.
If you wish to disable this notification, run:
odo preference set UpdateNotification false
---

[datho7561]

I tried using odo 3.4.0, and it doesn't output the podman version when you run odo version.

I tried putting odo 3.4.0 on path, but OpenShift still uses odo 3.14.0.

There is a setting "openshiftToolkit.searchForToolsInPath": true, to force using the odo from PATH, but this setting doesn't seem to work. (it still uses the odo bundled with the extension).

I did this all on Linux, I'll try it on Windows after lunch.

[datho7561]

I couldn't replicate the problem on Windows either

[jeffmaury]

It's not about odo 3.4 0 it's about bad diagnostic if podman is installed but no machine available

[datho7561]

Okay. I understand now and am able to reproduce the issue. I'll take a look into addressing it.