-
Notifications
You must be signed in to change notification settings - Fork 4
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
Ubuntu import 1.0-rc93 #5
Conversation
runc now has special handling for seccomp profiles to avoid making new syscalls unusable for glibc (LP: #1916485).
Weird, it does not FTBFS on armhf in Debian: |
(otherwise this looks very benign to me, assuming it works with containerd and Docker 👍) |
197a7a5
to
ffe93bf
Compare
Thanks @tianon . I backported the same patch and it fixed the issue. I do not know why I did not see this patch before 🤦 I am testing everything using the PPA in the description (there you can find docker.io and containerd packages as well), I am going to wait for your +1 to move forward. |
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.
👍
Thanks! I am just waiting for the FFe approval to get it merged and uploaded. |
FFe was approved. |
Version 1.0.0~rc93 contains an important fix for this bug:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916485
I uploaded the package to this PPA:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/docker-20.10/+packages
As you can see it FTBFS on armhf, there is an integer overflow in the test of the fix we want. I filed an upstream bug here:
opencontainers/runc#2846
I considered to skip this test for now, but since the failing test is seccomp related, which we want to make sure it is working, I turned it down. Let me know if you have a better approach for this issue.
FWIW autopkgtest is still happy on amd64: