Kir Kolyshkin 049a5f76cf libct/cap: allow New(nil) ...

In runtime-spec, capabilities property is optional, but
libcontainer/capabilities panics when New(nil) is called.

Because of this, there's a kludge in finalizeNamespace to ensure
capabilities.New is not called with nil argument, and there's a
TestProcessEmptyCaps to ensure runc won't panic.

Let's fix this at the source, allowing libct/cap to work with nil
capabilities.

(The caller is fixed by the next commit.)

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

2025-02-11 18:01:30 -08:00

..

capabilities_linux_test.go

Switch to github.com/moby/sys/capability v0.4.0

2024-12-02 13:18:10 -08:00

capabilities_unsupported.go

remove pre-go1.17 build-tags

2024-06-29 15:45:25 +02:00

capabilities.go

libct/cap: allow New(nil)

2025-02-11 18:01:30 -08:00