stage1: build a static compiled version

[philips]

We have two annoying options to get around this:

1. Chroot into the stage1 which makes doing bind mounts more annoying

2. Statically compile the stage1 so it doesn't depend on the host. Also patch out the stupid logic to check /run/systemd/system and talk to dbus to get the machine-id.

/cc @eyakubovich Where is that machine-id thing you were talking about? Can you add some more info on this?

[philips]

I worked on a prototype to use a static chroot'd stage1 to execute from1 but I ended up getting errors about mount MS_MOVE returning -EINVAL when execing nspawn. This needs some investigation.

/cc @vcaputo

[eyakubovich]

systemd-nspawn uses /etc/machine-id to generate a MAC address for the veth. They mix that with container_id (and then hash it) to produce a quasi-unique MAC for the veth.

[vcaputo]

The 3rd obvious option is to simply execute systemd-nspawn with LD_LIBRARY_PATH set to our libs, this gives us the same level of host-independence statically linking systemd-nspawn would give.

[vcaputo]

This should be an improvement and eliminates that mkdirall:
#149

[jonboulle]

This should be resolved by #149 and friends.