From fc32bf693d8b5df77927f79a550ce6944cca70ef Mon Sep 17 00:00:00 2001 From: "Hongli Lai (Phusion)" Date: Tue, 12 Nov 2013 12:55:16 +0100 Subject: [PATCH] Fix README --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 4e9f025..aafcc97 100644 --- a/README.md +++ b/README.md @@ -32,6 +32,12 @@ Why use baseimage-docker instead of doing everything yourself in Dockerfile? Baseimage-docker is very lightweight: it only consumes 4 MB of memory. +### Wait, I thought Docker is about running a single process in a container? + +Absolutely not true. Docker runs fine with multiple processes in a container. In fact, there is no technical reason why you should limit yourself to one process - it only makes things harder for you and breaks all kinds of essential system functionality, e.g. syslog. + +Baseimage-docker *encourages* multiple processes through the use of runit. + ## Inspecting baseimage-docker To look around in the image, run: @@ -40,12 +46,6 @@ To look around in the image, run: You don't have to download anything manually. The above command will automatically pull the baseimage-docker image from the Docker registry. -### Wait, I thought Docker is about running a single process in a container? - -Absolutely not true. Docker runs fine with multiple processes in a container. In fact, there is no technical reason why you should limit yourself to one process - it only makes things harder for you and breaks all kinds of essential system functionality, e.g. syslog. - -Baseimage-docker *encourages* multiple processes through the use of runit. - ## Using baseimage-docker as base image The image is called `phusion/baseimage`, and is available on the Docker registry.