diff options
| author | Daniel J Walsh <dwalsh@redhat.com> | 2020-10-28 10:27:31 -0400 |
|---|---|---|
| committer | Daniel J Walsh <dwalsh@redhat.com> | 2020-10-29 06:19:21 -0400 |
| commit | 0f191ad72c406cfe8223946c069f6ec70f559664 (patch) | |
| tree | 3ada37ecc5b6b666492303eeaf4f3d67f0b9c97f /test/e2e/build_test.go | |
| parent | cce6c6cd40137c460f173300b36c5868383870c5 (diff) | |
| download | podman-0f191ad72c406cfe8223946c069f6ec70f559664.tar.gz podman-0f191ad72c406cfe8223946c069f6ec70f559664.tar.bz2 podman-0f191ad72c406cfe8223946c069f6ec70f559664.zip | |
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>
Diffstat (limited to 'test/e2e/build_test.go')
0 files changed, 0 insertions, 0 deletions