I'm following the CoreOS Docker Documentation and it mentions starting containers with commands like:
docker run someImageName /bin/somebinary
someImageName is an image. When /bin/somebinary exits, the image will no longer be running.
I would simply like to run an image, without specifying any binaries to run. Instead, I simply want to run the services (eg, systemd / sysvinit) that are normally run inside the images OS.
This seems like the most common thing anyone would ever want to do with Docker, but trying to run an image without a command returns:
2014/02/05 14:49:19 Error: create: No command specified
How can I start a Docker container and run a full OS, rather than specifying a command?