walters added a new comment to an issue you are following:
``
Hm, so that's an assertion inside glibc. The obvious potential culprit here is that
bwrap is calling `sys_clone` behind glibc's back. But, it feels like this must either
be a race condition, or a change in glibc, since I'm simply not reproducing it;
scenario is
```
$ rpm -q glibc
glibc-2.24-4.fc25.x86_64
$ for x in $(seq 100); do bwrap --unshare-all --ro-bind / / sleep 1h & done
```
Gives me 100 containers every time. Does it reliably fail that way? Can you try running
that for loop in the root? And can you get the updated root.log? Is there anything in
there that's not in current updates-testing?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6602