Kir Kolyshkin 794cd66df8 libct/system: Exec: wrap the error ...

If the container binary to be run is removed in between runc create
and runc start, the latter spits the following error:

> can't exec user process: no such file or directory

This is a bit confusing since we don't see what file is missing.

Wrap the unix.Exec error into os.PathError, like in many other cases,
to provide some context. Remove the error wrapping from
(*linuxStandardInit).Init as it is now redundant.

With this patch, the error is now:

> exec /bin/false: no such file or directory

Reported-by: Daniel J Walsh <dwalsh@redhat.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

2021-10-07 11:09:08 -07:00

..

linux.go

libct/system: Exec: wrap the error

2021-10-07 11:09:08 -07:00

proc_test.go

libct/system.Stat: fix/improve/speedup

2021-08-19 19:48:39 -07:00

proc.go

libct/system: add I and P process states

2021-08-19 19:49:18 -07:00

syscall_linux_32.go

*: add go-1.17+ go:build tags

2021-08-30 20:58:22 -07:00

syscall_linux_64.go

*: add go-1.17+ go:build tags

2021-08-30 20:58:22 -07:00

xattrs_linux.go

*: ignore errorlint warnings about unix.* errors

2021-06-22 16:09:47 -07:00