Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The path to gvproxy is hardcoded to /usr/libexec/podman #11531

Closed
afbjorklund opened this issue Sep 11, 2021 · 4 comments · Fixed by #11449
Closed

The path to gvproxy is hardcoded to /usr/libexec/podman #11531

afbjorklund opened this issue Sep 11, 2021 · 4 comments · Fixed by #11449
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine

Comments

@afbjorklund
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

The path is hardcoded, which becomes a problem on systems that don't have it.

Such as Debian (/usr/lib/podman) or macOS (/usr/local/bin). It should be config ?

Steps to reproduce the issue:

  1. podman machine start

Describe the results you received:

Error: unable to start host networking: "start /usr/libexec/podman/gvproxy: no such file or directory"

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Looked like a known problem:

       // TODO we may wish to configure the directory in containers common
        binary := filepath.Join("/usr/libexec/podman/", machine.ForwarderBinaryName)

Output of podman version:

podman version 4.0.0-dev

Output of podman info --debug:

(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):

(paste your output here)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes/No

Additional environment details (AWS, VirtualBox, physical, etc.):

macOS
@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 11, 2021
@afbjorklund afbjorklund mentioned this issue Sep 11, 2021
Merged
@Luap99 Luap99 added the machine label Sep 11, 2021
@mheon
Copy link
Member

mheon commented Sep 12, 2021

This is exclusively a problem on main. The v3.3 branch uses different logic, which I believe @baude is going to forward-port to the main branch.

@afbjorklund
Copy link
Contributor Author

afbjorklund commented Sep 12, 2021 •
edited
Loading

Oh, I didn't know you did development on the branch

440188f

@afbjorklund
Copy link
Contributor Author

afbjorklund commented Sep 12, 2021 •
edited
Loading

Duplicate of: Issue #11226

@afbjorklund
Copy link
Contributor Author

Apparently the debian packages still install in /usr/libexec, even if it is against the FHS policy.

@simnalamburt simnalamburt mentioned this issue Sep 14, 2021
Merged
simnalamburt added a commit to simnalamburt/podman that referenced this issue Sep 14, 2021
@simnalamburt
Search gvproxy with config.FindHelperBinary()
072b061 
Closes containers#11531

[NO TESTS NEEDED]

Signed-off-by: Hyeon Kim <simnalamburt@gmail.com>
mheon pushed a commit to mheon/libpod that referenced this issue Sep 16, 2021
@simnalamburt @mheon
Search gvproxy with config.FindHelperBinary()
33591c3 
Closes containers#11531

[NO TESTS NEEDED]

Signed-off-by: Hyeon Kim <simnalamburt@gmail.com>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make gvproxy path configurable with containers.conf simnalamburt/podman
3 participants
@mheon @afbjorklund @Luap99