This is not used since commit dac4171.
It will be removed in v1.2.0

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
(cherry picked from commit dbd0c33)
Signed-off-by: lifubang <lifubang@acmcoder.com>

Do not refer to the function which was removed.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
(cherry picked from commit bac5064)
Signed-off-by: lifubang <lifubang@acmcoder.com>

Issue: opencontainers#4195
Since https://go-review.googlesource.com/c/go/+/476097, there is
a get/set race between runc exec and syscall.rlimit.init, so we
need to call setupRlimits after syscall.rlimit.init() completed.

Signed-off-by: lifubang <lifubang@acmcoder.com>
(cherry picked from commit a853a82)
Signed-off-by: lifubang <lifubang@acmcoder.com>

The complete generic features are supported since go 1.18

Signed-off-by: lfbzhm <lifubang@acmcoder.com>

As reported in issue opencontainers#4195, the new version(since 1.19) of go runtime
will cache rlimit-nofile. Before executing execve, the rlimit-nofile
of the process will be restored with the cache. In runc, this will
cause the rlimit-nofile set by the parent process for the container
to become invalid. It can be solved by clearing the cache.

Signed-off-by: ls-ggg <335814617@qq.com>
(cherry picked from commit f9f8abf)
Signed-off-by: lifubang <lifubang@acmcoder.com>
(cherry picked from commit da68c8e)
Signed-off-by: lifubang <lifubang@acmcoder.com>

issues:
opencontainers#4195
opencontainers#4265 (comment)

Signed-off-by: lifubang <lifubang@acmcoder.com>
(cherry picked from commit 4ea0bf8)
Signed-off-by: lfbzhm <lifubang@acmcoder.com>

Signed-off-by: lifubang <lifubang@acmcoder.com>
(cherry picked from commit a35f7d8)
Signed-off-by: lifubang <lifubang@acmcoder.com>