I installed it, ran it, and it immediately complained "not a systemd system" and refused to run. I've not looked into things further, but presumably systemd-nspawn requires that systemd be running, which was a surprise to me since systemd-nspawn calls itself "chroot on steroids", and chroot cares nothing about the init system.
If I remember correctly, systemd-nspawn uses cgroups (hence the "steroids" part of of "chroot on steroids").
On Linux, cgroups require a single manager for all cgroups (in this case systemd). This is not a systemd limitation; it is a requirement set by the Linux kernel[0].
In theory you could bring-your-own cgroup manager, but cgroups are nascent enough that trying to make a userland tool like systemd-nspan work with a completely pluggable cgroup manager would be a nightmare.
[0] http://www.freedesktop.org/wiki/Software/systemd/ControlGrou...
[1] https://www.kernel.org/doc/Documentation/cgroups/cgroups.txt
http://man7.org/linux/man-pages/man2/unshare.2.html
http://man7.org/linux/man-pages/man2/clone.2.html
http://man7.org/linux/man-pages/man1/unshare.1.html
Loosely a "container" (in the LXC or Docker sense) is a combination of making new namespaces, which isolate the process tree from the rest of the system in various ways (filesystem, network, hostname as returned by "uname", etc.), and making a cgroup, which allows for process tracking and resource allocation.