[06:28] <mitya57> ahayzen: thanks. I don’t have time to investigate so far, but my initial guess is that the containers may be blocking the syscalls that are important to Qt.
[06:29] <mitya57> (Like in Debian #901062)
[10:02] <ahayzen> mitya57, no worries, right it's going to be something funky :-) The interesting part is that the same .run works on an older container, so something to do with the 18.04 container and it's env. Let me know if there is any additional info i can try to extract
[10:43] <ahayzen> Also note that to use gdb inside docker i am passing "--security-opt seccomp=unconfined" which should not block certain syscalls, as described in the bug report you linked. And that older versions like Qt 5.6 have similar issues on 18.04
[14:31]  * lisandro suspects we will be seeing more containers issues with Qt in the near future
[14:31] <lisandro> it's amazing the amount of times I have seen this in the last two weeks
[15:03] <acheronuk> :/
[15:26] <lisandro> I think it is actually rather a good thing
[15:27] <lisandro> like creating docker images from testing/sid and using them in stable