Kir Kolyshkin 42cea2ecb4 libct: don't allow to start second init process ...

By definition, every container has only 1 init (i.e. PID 1) process.

Apparently, libcontainer API supported running more than 1 init, and
at least one tests mistakenly used it.

Let's not allow that, erroring out if we already have init. Doing
otherwise _probably_ results in some confusion inside the library.

Fix two cases in libct/int which ran two inits inside a container.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

2024-06-10 22:30:03 -07:00

..

checkpoint_test.go

libct/int: checkpoint test: skip pre-dump if not avail

2024-05-10 11:04:58 -07:00

doc.go

Move libcontainer into subdirectory

2015-06-21 19:29:15 -07:00

exec_test.go

update/add some tests for rlimit

2024-05-08 10:57:10 +00:00

execin_test.go

libct: don't allow to start second init process

2024-06-10 22:30:03 -07:00

init_test.go

libct/init: unify init, fix its error logic

2023-08-04 13:00:35 -07:00

seccomp_test.go

init: verify after chdir that cwd is inside the container

2024-01-24 00:20:58 +11:00

template_test.go

Capitalize [UG]idMappings as [UG]IDMappings

2023-07-21 13:55:34 +02:00

update_test.go

libct/int: adapt to Go 1.15

2021-07-27 01:41:47 -07:00

utils_test.go

libc/int: add/use runContainerOk wrapper

2023-02-22 02:58:47 -08:00