** Description changed: + ================================================================ + Impact: restoring containers from a checkpoint doesn't work + Development fix: LXC uses /usr/lib/x86_64-linux-gnu/lxc as the path to moun the container's root filesystem in its private mount namespace before it pivot_roots during restore. Unfortunately, that's also the location of the lxc-restore-net script which criu tries to execute. Since at this point the container's fs has already been mounted there, the callback (and thus the restore) fails. + Stable fix: Same as development fix + Testcase: create a container, then do: + sudo lxc-checkpoint -n $foo -s -D /tmp/checkpoint + sudo lxc-checkpoint -r -n $foo -D /tmp/checkpoint + + The restore fails with, + + sh: 1: /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found + + Regression potential: This can't effect anything besides lxc-checkpoint -r, which is broken anyways, so there should be no regressions. + ================================================================ + + A patch for this has been posted to the upstream LXC list here: https://lists.linuxcontainers.org/pipermail/lxc- devel/2014-October/010741.html
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
