as Michael Hampton mentioned, containers are meant to run only single atomic service. As a matter of fact, one should understand that containers are not virtual machines but a single process by itself on your localhost.
Nevertheless, I got to know that, its a bit more harder to get SystemD working inside a container from here
I was able to get SystemD working inside an image built FROM
docker run --privileged -ti -e "container=docker" -v
For some undocumented reason the variable
container=docker is apparently required. /sys/fs/cgroup is also
required, as SystemD needs cgroups to work properly according to
RedHat Bug 1033604.
After doing this, try to login to the container using
docker exec -it <container> /bin/bash and then you could execute your