4 Jun
2021
4 Jun
'21
4:09 p.m.
On 6/4/21 6:34 PM, Peter Dimov via Boost wrote:
Andrey Semashev wrote:
<rant> Docker people seem to think of Docker images as of VMs while they are not. Hence they consider it normal to build the image on one system and then run it on another, with possibly older kernel. Well, this is wrong. It doesn't work that way, and Boost.Filesystem is not the only piece of software that will break because of that. </rant>
As Niall mentioned, it might be that Docker just doesn't support the syscalls, even when running on the same kernel.
This is a different case, and for that I added compile-time options to disable some syscalls in Boost.Filesystem.