libc 2.31/i686: operation not permitted for preserving timestamps

[Arkadiusz Miśkiewicz]

On 18/04/2020 08:32, Elan Ruusamäe wrote:
> 
> On 4/3/20 9:47 PM, Arkadiusz Miśkiewicz wrote:
>> On 03/04/2020 20:09, Elan Ruusamäe wrote:
>>> is this fix for this problem?
>>>
>>> -
>>> https://github.com/pld-linux/util-linux/commit/67a912cd50464cae095fbdb7b3cf90daf495fb90
>>>
>>>
>>>
>>> -
>>> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025883.html
>>>
>> No.
>>
>> Do you use systemd-nspawn for starting something and running cp inside?
>>
>> Is that cp test on vm/bare metal + kernel + just userspace directly?
>>
> it's inside docker, as noted in earlier post:
> 
> -
> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2020-March/025887.html
> 
> 
> - here's full build log attemting to  build base image:
> 
> 
> https://gitlab.com/pld-linux/pld/-/jobs/480110124
> 
> 
> the reproducer is pretty straight forward, and i don't think it matters
> what is the host kernel. it fails in that cloud and fails in docker for
> mac (O)
> 
> 
> ```
> 
> $ docker run --rm -it
> registry.gitlab.com/pld-linux/pld/i686 at sha256:832f004cc28798aafd758a7e6aa867681f1f860ac22b341dc8a2183a75a53e36
> bash

What happens if you start docker also with --security-opt
seccomp=unconfined ?

And with libseccomp 2.4.3 but without above option?

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )