packages/utils/oci-runtime-tools/patches, branch master

oci-runtime-tools: adapt the tests to the host kernel

2026-10-22T13:06:39Z

The hugetlb tests fail on kernels without huge pages or the hugetlb cgroup controller, and the rlimit test sets limits of 4 GiB and more that a 32-bit kernel turns into RLIM_INFINITY, so they fail against every runtime on most OpenWrt targets. Carry the pending upstream fixes that skip the hugetlb tests on such kernels, report a refused hugetlb container as a failed test and leave out the rlimits the host cannot hold. Link: https://github.com/opencontainers/runtime-tools/pull/823 Signed-off-by: Daniel Golle

oci-runtime-tools: carry the pending validation fixes

2026-10-20T19:03:57Z

Most cgroup tests fail on OpenWrt because the test suite can only read cgroup v1, and several assertions contradict the runtime-spec or depend on the test host. Carry the fixes pending upstream in opencontainers/runtime-tools until they are merged: #812 (cgroup v2 reader), #813 (lifecycle assertions), #814 (pids limit by value), #816 (device rules checked from inside the container), #820 (misc_props process), #821 (blkio rules on an existing block device) and #822 (RLIMIT_NOFILE read from a child process). The default seccomp profile of the test configurations lists only the 32-bit time syscalls. On 32-bit targets the Go runtime of runtimetest uses futex_time64 on Linux 5.1 and later, which the profile denies, so runtimetest crashes inside every container and most tests report nothing on i386. Add a patch allowing the time64 variant of every syscall the profile already allows. Signed-off-by: Daniel Golle

oci-runtime-tools: bump to git HEAD

2021-03-26T19:41:21Z

Remove local patch which was merged upstream. Signed-off-by: Daniel Golle

treewide: Run refresh on all packages

2021-02-21T00:02:15Z

The crude loop I wrote to come up with this changeset: find -L package/feeds/packages/ -name patches | \ sed 's/patches$/refresh/' | sort | xargs make Signed-off-by: Ilya Lipnitskiy

oci-runtime-tools: add package

2021-02-08T01:39:32Z

Package oci-runtime-tool itself as well as oci-runtime-tests containing runtime validation test executables as well as rootfs tarballs used by the tests. oci-runtime-tool can be used to generate OCI spec files or validate OCI bundles. To validate the OCI runtime (runc, crun, uxc, maybe others) itself, install the 'oci-runtime-tests' package as well as 'node-npm', use npm to install node-tap and symlink the tap executable to /usr/bin. Then cd /usr/libexec/oci-runtime-tests tap *.t Signed-off-by: Daniel Golle