This bug is caused by the new nsroot= patch introduced in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560489
To fix it, we have two options:
1. patch the kernel again to allow nsroot= to be supplied on mount (I've spoken to hallyn and he's going to write a patch to allow this soon)
2. patch CRIU (with a patch that won't go upstream in CRIU, because we're expecting the mount patch from 1 to land) to trim nsroot before restoring: https://github.com/tych0/criu/commit/5691a6b38c84d23707008d465bbb25ef3c8a57eb
In either case, we also need to apply this patch to CRIU: https://github.com/xemul/criu/commit/d071ab161a7a147673253a4f460c1f1164acd470
This bug is caused by the new nsroot= patch introduced in:
https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1560489
To fix it, we have two options:
1. patch the kernel again to allow nsroot= to be supplied on mount (I've spoken to hallyn and he's going to write a patch to allow this soon)
2. patch CRIU (with a patch that won't go upstream in CRIU, because we're expecting the mount patch from 1 to land) to trim nsroot before restoring: https:/ /github. com/tych0/ criu/commit/ 5691a6b38c84d23 707008d465bbb25 ef3c8a57eb
In either case, we also need to apply this patch to CRIU: https:/ /github. com/xemul/ criu/commit/ d071ab161a7a147 673253a4f460c1f 1164acd470