Podman often reports OCI Runtime does not exist, even if it does

When the OCI Runtime tries to set certain settings in cgroups
it can get the error "no such file or directory",  the wrapper
ends up reporting a bogus error like:

```
 Request Failed(Internal Server Error): open io.max: No such file or directory: OCI runtime command not found error
{"cause":"OCI runtime command not found error","message":"open io.max: No such file or directory: OCI runtime command not found error","response":500}
```

On first reading of this, you would think the OCI Runtime (crun or runc) were not found.  But the error is actually reporting

message":"open io.max: No such file or directory

Which is what we want the user to concentrate on.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/libpod/define/errors.go b/libpod/define/errors.go
index 627928ef7..5567d1838 100644
--- a/libpod/define/errors.go
+++ b/libpod/define/errors.go
@@ -138,15 +138,15 @@ var (
 
 	// ErrOCIRuntimePermissionDenied indicates the OCI runtime attempted to invoke a command that returned
 	// a permission denied error
-	ErrOCIRuntimePermissionDenied = errors.New("OCI runtime permission denied error")
+	ErrOCIRuntimePermissionDenied = errors.New("OCI permission denied")
 
 	// ErrOCIRuntimeNotFound indicates the OCI runtime attempted to invoke a command
 	// that was not found
-	ErrOCIRuntimeNotFound = errors.New("OCI runtime command not found error")
+	ErrOCIRuntimeNotFound = errors.New("OCI not found")
 
 	// ErrOCIRuntimeUnavailable indicates that the OCI runtime associated to a container
 	// could not be found in the configuration
-	ErrOCIRuntimeUnavailable = errors.New("OCI runtime not available in the current configuration")
+	ErrOCIRuntimeUnavailable = errors.New("OCI unavailable")
 
 	// ErrConmonOutdated indicates the version of conmon found (whether via the configuration or $PATH)
 	// is out of date for the current podman version