rsync copyed systemd-nspawn container won't start

[basti <mailinglist@unix-solution.de>]

Hello,

i have copy a running systemd-nspawn container via rsync.
The container won't start in the destination:

Jan 11 15:22:55 dhanna systemd[1]: Started Container foo.
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: systemd 232 running in
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GC
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Detected virtualization
systemd-nspawn.
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Detected architecture x86-64.
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: [1B blob data]
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Welcome to Debian
GNU/Linux 9 (stretch)!
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: [1B blob data]
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Set hostname to <foo>.
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Failed to install release
agent, ignoring: No such file or directory
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Failed to create
/init.scope control group: Operation not permitted
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Failed to allocate manager
object: Operation not permitted
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: [!!!!!!] Failed to
allocate manager object, freezing.
Jan 11 15:22:55 dhanna systemd-nspawn[21268]: Freezing execution.


Then I try it with

debootstrap --variant=minbase --include
systemd,vim,libterm-readline-gnu-perl,iproute2,dialog,dbus stretch
/var/lib/machines/foo

it work as expected.

Any ideas?

Best regards