podman binary name

[gbraad]

The inclusion of the podman client is very inconsistent; as for Linux this can be the full implementation, while on macOS/Windows this is podman-remote.

When considering convenience and consistent use we want to settle on a single command; podman. This has been brought up before.

crc-org/snc#378

[gbraad]

/cc: @fatherlinux, @baude, WDYT?

[gbraad]

We will use podman-remote as according to our @code-ready/crc-team sync-up

[cfergeau]

Is there an upstream issue regarding the inconsistent naming?

[gbraad]

@cfergeau this is what I could find containers/podman#5477 (comment) and there has been an email conversation around this.

[gbraad]

The interesting reply is: containers/podman#5477 (comment)

---

@rhatdan wrote:
Yes I agree, the executable should be podman.exe not podman-remote-windows.exe

---

The V2.2.1 releases are:

• macOS: podman-remote-release-darwin.zip
  • podman
• Windows: podman-remote-release-windows.zip
  • podman.exe
• Linux: podman-remote-static.tar.gz
  • podman-remote-static

So there is still an inconsistency between what the platforms provide as binary/command for inclusion. From our perspective a single option should be given, as else this needs to be documented differently for the platforms. Some of these specifics can be found in the bundle inclusion code: https://github.com/code-ready/snc/pull/378/files#diff-95795afe77d69420567b1e1e44ff75e9dd179f9caaaa51eefa0581e1fc1067f0

My biggest concern is around how this experience will be to the user when they use the podman-env command and how to document this. On Windows we use podman.exe, but on Linux podman-remote to prevent a possible conflict with the current installed version?

[guillaumerose]

containers/podman#9918 confirms what I have in crc-org/snc#378

Linux: podman-remote
macOS: podman
Windows: podman.exe

[gbraad]

While correct what @vrothberg concludes, this would lead to an inconsistency for use on #Linux if we expose this as a command.

podman-env would add to path, and would have to instruct the user based on the OS to either use podman or podman-remote, and this also needs to be documented accordingly. To me this feels like a bad UX.

Note: In our case we are always performing a remote session, while NOT as nice a command, it would be consistent to use podman-remote. Also, you can't assume a podman command to exist on Linux is the user might not have installed this (and if he did, why would he use crc)? So, do we really care about a command clash?

[gbraad]

containers/podman#9381

[cevich]

#9381 is almost ready, doing final testing and tweaking now.

[guillaumerose]

In 1.26.0:
Linux: podman-remote
macOS: podman
Windows: podman.exe