-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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.
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
[3.0.1] podman build started failing with "runc: executable file not found in $PATH" although runc is in a recognized location #9459
Comments
@rhatdan, we need to consolidate the runtime-selection code into |
We need to pass the container runtime from podman to buildah podman build --runtime crun ... We fixed an issue in podman 3.0.1 for this, and looks like we are triggering a new bug. |
@rhatdan I'm fairly sure this is more than that - I think Buildah is resolving the runtime differently than Podman, just using $PATH and not using the dedicated runtimes list in |
I share that thought, that's why I want us to consolidate the code in |
Just confirming this is what I mentioned in #9365 (comment). Apologies that I didn't have time to open a new issue for it. In my case, I installed
but it is not in
Default behavior:
Manually passing path to runtime:
Ensuring runtime is in
edit to add:
|
A friendly reminder that this issue had no activity for 30 days. |
[NO TESTS NEEDED] Mainly because I have no idea how we would test this. Fixes: containers#9459 Signed-off-by: Daniel J Walsh <[email protected]>
[NO TESTS NEEDED] Mainly because I have no idea how we would test this. Fixes: containers#9459 Signed-off-by: Daniel J Walsh <[email protected]>
[NO TESTS NEEDED] Mainly because I have no idea how we would test this. Fixes: containers#9459 Signed-off-by: Daniel J Walsh <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman build ...
with a Containerfile started failing withexec: "runc": executable file not found in $PATH
.Indeed
runc
is not in $PATH but in one of the locations listed in theengine.runtimes.runc
config option.podman info
picks it up correctly (see below).buildah bud ...
(with runc configured) works correctly (buildah 1.19.6)Steps to reproduce the issue:
Make sure podman uses runc
Describe the results you received:
podman build ...
fails with an unexpected error:Describe the results you expected:
Should build a container as it did before and as it does with buildah
Additional information you deem important (e.g. issue happens only occasionally):
This worked in Podman 3.0.0.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):The text was updated successfully, but these errors were encountered: