switch to systemd /sbin/init for services

[james-nesbitt]

There are some disadvantages to running direct services on command line that would be solved by switching to using systemd to run all container services.

Disadvantages:

• it seems that running using systemd would require a specific mount to be used on any containers;
• scanning the docker container list wont show you what binary is running
• running a single service per container is the old-school "best-practice" in the docker world

Advantages:

• no more zombie processes
• better handling of services,
• better options for startup scripts for custom actions and binary preparation
• most services already come with a systemd service (no scripts required.)

[james-nesbitt]

I have a systemd branch started: https://github.com/james-nesbitt/wunder-docker/tree/systemd

[james-nesbitt]

so far the base image has been reformatted to use systemd, and the nginx image runs.

This may be refactored so that there are 2 base images: base & base-systemd

[james-nesbitt]

The biggest impact here is that any container run from these images would have a runtime requirement for mounting. I am pretty sure that this makes them useless.