d80dbdae68
The current code simply ignores the full binary path when starting the shimv2 process, and instead fallbacks to a binary in the path, and this is problematic (and confusing) for those using CRI-O, which has this bits vendored. The reason it's problematic with CRI-O is because the user can simply set the full binary path and, instead of having that executed, CRI-O will simply fail to create the container unless that binary is part of the path, which may not be case in a few different scenarios (testing being the most common one). Fixes: #5006 Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> |
||
|---|---|---|
| .. | ||
| publisher.go | ||
| shim_darwin.go | ||
| shim_freebsd.go | ||
| shim_linux.go | ||
| shim_test.go | ||
| shim_unix.go | ||
| shim_windows.go | ||
| shim.go | ||
| util_unix.go | ||
| util_windows.go | ||
| util.go | ||