You've already forked runc
mirror of
https://github.com/opencontainers/runc.git
synced 2026-10-23 19:49:01 +03:00
Run podman tests using runc as the OCI runtime, similar to what crun does in its CI: - podman e2e tests (test/e2e); - a subset of podman system tests (test/system/*.bats), the same one that crun runs (via podman-tests in tmt), both as root and rootless. Run e2e, system, and rootless system tests as separate jobs. Podman is built from source (v5.8.8), while its runtime dependencies (conmon, netavark, containers-common, CRIU etc.) come from Ubuntu 26.04 packages. CRIU is installed to enable podman checkpoint/restore tests. Since system tests use podman's default runtime, configure it to be runc, and make sure it actually is before running tests. Some tests are skipped as they are either flaky, do not test the runtime, or do not work in GitHub Actions environment. Ubuntu 26.04 specifics: - switch from sudo-rs to the original sudo, as we need sudo -E; - do not use -Werror (which we set globally) when building podman, as it fails to compile its bundled sqlite with newer glibc; - set NETAVARK_FW=iptables, since the GHA image sets firewall_driver to iptables via a containers.conf.d drop-in, which is not used by tests that set CONTAINERS_CONF, resulting in mixed nftables/iptables setup/teardown and flaky network teardown failures; - skip "podman run with noexec can't exec" test, which uses /bin/ls from the host, which is a symlink to a binary in another directory on Ubuntu 26.04 (a fix is proposed to podman). Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>