Comment 2 for bug 1867675

We ran into the same issue in the containerd packaging scripts (, 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.