More details on this bug:
# touch /lib/systemd/network/80-container-host0.network.dpkg-new
touch: cannot touch '/lib/systemd/network/80-container-host0.network.dpkg-new':
No such file or directory
# touch /lib/systemd/network/80-container-hodt0.network.dpkg-new
# rm -f /lib/systemd/network/80-cont
I thought the same initially, but the directory is there. And I can
create any file, except /lib/systemd/network/80-container-host0.network
.dpkg-new:
# ls -l /lib/systemd/network/
total 8
-rw-r--r-- 1 root root 0 Sep 16 06:56 80-container-hst0.dpkg-new.a
-rw-r--r-- 1 root root 482 Sep 16 06:41
No, that is an RimuHosting kernel.
I've switched to an Ubuntu kernel, still the same results:
# grep -i trace /proc/self/status
TracerPid: 0
# uname -a
Linux XXX.XXX 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:58:34 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
# strace true
[-] Error 0x
