That sounds a plausible reason. Preventing change of target name when migrating a running container would be a reasonable temporary solution.
So I retried, this time keeping the target container name the same. However it failed again, but with a different error: root@nuc1:~# lxc move sample nuc2:sample error: Error transferring container data: restore failed: (00.213976) 1: Error (mount.c:2406): mnt: Can't mount at ./sys/kernel/debug: Invalid argument (00.229795) Error (cr-restore.c:1352): 4333 killed by signal 9 (00.272166) Error (cr-restore.c:2182): Restoring FAILED. Running again with inotifywait on the target: root@nuc2:~# inotifywait -mr /var/lib/lxd/shmounts Setting up watches. Beware: since -r was given, this may take a while! Watches established. /var/lib/lxd/shmounts/ CREATE,ISDIR sample /var/lib/lxd/shmounts/ OPEN,ISDIR sample /var/lib/lxd/shmounts/ ACCESS,ISDIR sample /var/lib/lxd/shmounts/ CLOSE_NOWRITE,CLOSE,ISDIR sample /var/lib/lxd/shmounts/sample/ DELETE_SELF /var/lib/lxd/shmounts/ DELETE,ISDIR sample Let me know if you want this opening as a separate issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580765 Title: Need support for rewriting mount sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/criu/+bug/1580765/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
