-
Notifications
You must be signed in to change notification settings - Fork 18
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
Ubuntu package cri-o-runc has wrong path #14
Comments
@lsm5 do we ship a runc package for Ubuntu? |
@rhatdan yes it's called 'cri-o-runc'. @everflux we don't want to conflict with distro's own runc, so that's why the non-standard location. @TomSweeneyRedHat didn't we fix this already? Or was this issue forgotten? |
Would be cool if I can force buildah to use that cri-o-runc, but export the additional PATH did not help. |
@everflux I'll look up my build files in a bit, and will get it fixed there if doable, else @TomSweeneyRedHat might need to step in. |
YOu could also use the --runtime flag |
@lsm5 whack me up side the head as necessary, I think this one we had a number of discussions on and then we both got distracted by other issues. In addition to the flag, @rhatdan also setup an env variable that can be used: BUILDAH_RUNTIME. That's just made its way into GitHub with containers/buildah#786 |
Correct, and this issue triggered it. |
When trying to use buildah to build an image using the PPA packages for ubuntu, the "runc" comand is not found and the build aborts.
The cri-o-runc package contains the runc executable, but at
/usr/lib/cri-o-runc/sbin/runc
which is not in the PATH.Linking is a workaround
sudo ln -s /usr/lib/cri-o-runc/sbin/runc /usr/local/sbin
but please place the runc command in the proper place.
The text was updated successfully, but these errors were encountered: