runtime validation: \"runc\" not found in $PATH: exec: \"runc\": executable file not found in $PATH" #4069
Description
Description
CRI-O fails when runc binary is not present in $PATH, even when [crio.runtime.runtimes] doesn't contain runc
Steps to reproduce the issue:
- Trigger Usernetes CI with CRIO_COMMIT= 267aa23 (2020-08-11): update components rootless-containers/usernetes#183
Describe the results you received:
...
Aug 12 07:31:41 a9fab463e670 crio.sh[449]: time="2020-08-12 07:31:41.219385057Z" level=info msg="Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_KILL"
Aug 12 07:31:41 a9fab463e670 crio.sh[449]: time="2020-08-12 07:31:41.219476364Z" level=fatal msg="Validating runtime config: runtime validation: \"runc\" not found in $PATH: exec: \"runc\": executable file not found in $PATH"
Aug 12 07:31:41 a9fab463e670 systemd[50]: u7s-crio.service: Main process exited, code=exited, status=1/FAILURE
Describe the results you expected:
Should work
Additional information you deem important (e.g. issue happens only occasionally):
It had been working with c1d5921 (2020-07-28).
Seems a regression in c1d5921...267aa23