kas-container: Fix podman detection#169
Conversation
When "docker -v" is ran and podman docker compatibility is enabled, podman will report the version string as "docker version x.x.x". Due to this the check will fail and report unknown engine.
|
Thanks for this fix. Please submit to the mainling list for further discussions if possible. Note already that you are changing the default if both podman and docker are installed, and that should be avoided or done explicitly (with reasoning). |
|
Just had a look at this again but on Debian. There is seems this enhanced emulation mode does not exist. Is it Nix-specific? Anyway, please follow up on my remarks, provide a signed-off patch (CONTRIBUTING.md), via the mailing list or at least here (will mirror it for you then). Thanks. |
|
Sorry, I forgot about this PR... This seems to be the behavior when Docker compatibility is just done by using a symlink. At least it's what it looks like nix does I tested with a fedora container and I get the same behavior: 
It looks like podman just uses $0 when identifying the version. I will sign the patch and send to the mailing list. |
2 participants
When "docker -v" is ran and podman docker compatibility is enabled, podman will report the version string as "docker version x.x.x". Due to this the check will fail and report unknown engine.