We ran into the same issue in the containerd packaging scripts (https://github.com/docker/containerd-packaging/pull/151), and it looks like the `Cannot utime: Operation not permitted` is caused by seccomp blocking something.
Now the question is if the default seccomp profile is blocking something that does not have to be blocked, if a different syscall is made when installing this package or if a syscall is made that is not understood by libseccomp (perhaps different syscalls were added for 32-bit platforms). Not an expert in this area, but thought I'd at least add the info I have at this moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867675 Title: Install failure for libc6 2.31-0ubuntu6 on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
