runc · Issues· 339 open

`--preserve-fds` leaks runc's own file descriptors when fewer FDs are actually passed

[rfc] crun extension compatibility

[tracking issue] deprecation of insecure --no-pivot flag

move most packages into `internal`

Support Landlock LSM?

checkProcMount() is too strict

Validate mount options for null bytes (\u0000) early to provide clearer error messages

Indefinite parent hang in ReadPacket upon abnormal child exit after procRun

In my test, the versions 1.2.8-1.4.1 of runc do not support the parameter "tty:true" for Kubernetes pods. The containers remain in the process of creation.

rshared propagation (bind mount options and rootfsPropagation) silently results in private mounts; Kubernetes mountPropagation=Bidirectional inert (runc 1.4.2)

Flaky test: TestFdLeaks

Feature Request: Support Two Phases to Start Exec Process like Init

Add an optional pre-exec wait FIFO to `runc exec`

`runc state` reports a CRIU-restored container as `running` after its process has exited

`root.readonly` is silently ignored (rootfs left writable) when the container has no mount namespace