Skip to content

Conversation

@mtrmac
Copy link
Contributor

@mtrmac mtrmac commented Dec 8, 2025

Testing a hypothesis for #533 .

l0rd and others added 7 commits December 1, 2025 18:10
The default helper binary directory on Windows was hardcoded. However
the new user-scope installer deploys the binaries on a distinct
directory. As a consequence `podman machine start` fails because
gvproxy/winssh-proxy cannot be found.

This problem affects Hyper-V, not WSL.

To fix the problem we are using $BINDIR that is used by the function
FindHelperBinaries to look in the directory where podman is located.

Fixes containers/podman#27603

Signed-off-by: Mario Loriedo <mario.loriedo@gmail.com>
…es-cp

[podman-5.7] Use $BINDIR as the default helper binary directory on Windows
When using http proxy vars in the engine section they can still get
leaked because http_proxy defaults to true.

Fixes: https://issues.redhat.com/browse/RHEL-127541

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
(cherry picked from commit d205608)
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
[podman-5.7] common: clarify containers.conf doc for env
Bump common to v0.66.1 in preparation for Podman v5.7

Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
Merge common/v0.66.1 tag into main so the go module resolver can update
newer digest instead of thinking v0.66.1 is newer.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@mtrmac mtrmac closed this Dec 9, 2025
@mtrmac mtrmac deleted the test-validation branch December 9, 2025 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants