-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: add actuated-arm64 #4142
CI: add actuated-arm64 #4142
Conversation
b47bb63
to
5c3e3ac
Compare
Thanks for the ping. The build should run once the GitHub app is installed. |
Thanks to @amye the app is now installed. |
715693c
to
c844665
Compare
Maybe it is enough to retry with the latest kernel. The latest error I see here is not related to restartable sequences and the files which are running in the test containers are using binaries from glibc 2.31 (busybox) and glibc 2.28 (debian). At this point, with the latest kernel, it might just work. |
Rebased. |
We have a 6.x Kernel on the roadmap, but it's a significant amount of labour and iteration to take a Firecracker guest Kernel and only enable the specific features for containers and ebpf, so if that resolves the issues with CRIU we will reach out when it's ready. I'd suggest you merge this PR and skip those tests for the time being on arm64. The project's test coverage on native hardware will be in a much better position already. Would you agree? |
Ping @opencontainers/runc-maintainers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, just one minor nit
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
kcmp is often missing: https://man7.org/linux/man-pages/man2/kcmp.2.html > Before Linux 5.12, this system call is available only if the > kernel is configured with CONFIG_CHECKPOINT_RESTORE, since the > original purpose of the system call was for the > checkpoint/restore in user space (CRIU) feature. (The > alternative to this system call would have been to expose > suitable process information via the proc(5) filesystem; this was > deemed to be unsuitable for security reasons.) Since Linux 5.12, > this system call is also available if the kernel is configured > with CONFIG_KCMP. Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
On cgroup v2, cpu burst needs kernel >= 5.14 torvalds/linux@f418371 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
See <https://actuated.dev/blog/arm-ci-cncf-ampere>. Thanks to Alex Ellis, Ampere Computing, and Equinix. Host information: * CPU: aarch64 (ARMv8) * Kernel: 5.10.201 * Lacks ~CONFIG_CHECKPOINT_RESTORE~, CONFIG_BLK_CGROUP_IOCOST, etc. * Cgroup: v2 * OS: Ubuntu 22.04 * Lacks newuidmap, newgidmap, etc. (still apt-gettable) * sshd is not running vmmeter is added from: https://gist.github.com/alexellis/1f33e581c75e11e161fe613c46180771#file-metering-gha-md Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Thanks @alexellis |
You're welcome. |
See https://actuated.dev/blog/arm-ci-cncf-ampere.
Thanks to Alex Ellis, Ampere Computing, and Equinix.
Host information:
,CONFIG_CHECKPOINT_RESTORE
CONFIG_BLK_CGROUP_IOCOST
, etc.newuidmap
,newgidmap
, etc. (still apt-gettable)sshd
is not running