I was I was two point releases behind at :
$ uname -a
Linux ses-docker50c 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
So I updated that machine to 4.15.0-36-generic, but I wanted to know what the status of this was. I think as a workaround I will use a docker mount for the entire build directory.
I think I just ran into this bug on bionic. I was building a yocto distribution like this user here: /www.spinics. net/lists/ linux-unionfs/ msg05363. html
https:/
I was I was two point releases behind at :
$ uname -a
Linux ses-docker50c 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
So I updated that machine to 4.15.0-36-generic, but I wanted to know what the status of this was. I think as a workaround I will use a docker mount for the entire build directory.