-
Notifications
You must be signed in to change notification settings - Fork 787
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
runc not found (debian, project karmic) #2113
Comments
@lsm5 PTAL |
@TomSweeneyRedHat remind me how buildah searches for runc? IIRC, podman has the paths available by default in a config file, can buildah reuse those? |
@lsm5 I believe we look for it in /usr/bin/runc |
and what's the right way to specify a non-default path? |
@TomSweeneyRedHat We should move to supporting it similarly to how podman does. We have containers.conf in the system now, so buildah should walk the list of runtimes and find one to make it work. |
So, debian's own |
@TomSweeneyRedHat or @lsm5 we have now merged containers/common into buildah, so could one of you open a PR to use the containers/common to figure out the runc to use, and match what podman is doing. |
I'll take a look this afternoon. |
After receiving the determing the type of runtime to use, either "runc" or "crun" dependent upon the system, search the list of that type of runtime in the containers.conf file. It includes the location of those runtimes in a number of different architectures. Once found, set the runtime to use to that value. Fixes: containers#2113 Signed-off-by: TomSweeneyRedHat <[email protected]>
After determining the type of runtime to use, either "runc" or "crun" dependent upon the system, search the list of that type of runtime in the containers.conf file. It includes the location of those runtimes in a number of different architectures. Once found, set the runtime to use to that value. Fixes: containers#2113 Signed-off-by: TomSweeneyRedHat <[email protected]>
After determining the type of runtime to use, either "runc" or "crun" dependent upon the system, search the list of that type of runtime in the containers.conf file. It includes the location of those runtimes in a number of different architectures. Once found, set the runtime to use to that value. Fixes: containers#2113 Signed-off-by: TomSweeneyRedHat <[email protected]>
After determining the type of runtime to use, either "runc" or "crun" dependent upon the system, search the list of that type of runtime in the containers.conf file. It includes the location of those runtimes in a number of different architectures. Once found, set the runtime to use to that value. Fixes: containers#2113 Signed-off-by: TomSweeneyRedHat <[email protected]>
2182: Search for local runtime per values in containers.conf r=rhatdan a=TomSweeneyRedHat After determining the type of runtime to use, either "runc" or "crun" dependent upon the system, search the list of that type of runtime in the containers.conf file. It includes the location of those runtimes in a number of different architectures. Once found, set the runtime to use to that value. Fixes: #2113 Signed-off-by: TomSweeneyRedHat <[email protected]> Co-authored-by: TomSweeneyRedHat <[email protected]>
Description
Basically the same as #1754 but with a different distro and package.
Buildah is unable to find
runc
. I have it at/usr/sbin/runc
from therunc
package provided by debian. It's normal for debian to not have the sbin paths onPATH
for normal users.Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Successful running of a command
Output of
rpm -q buildah
orapt list buildah
:Output of
buildah version
:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:(Does not exist)
The text was updated successfully, but these errors were encountered: