40n8.me/baseimage-docker
1
0
Fork 0
mirror of /repos/baseimage-docker.git synced 2025-12-30 08:01:31 +01:00
Code Issues Releases Wiki Activity

Fix README

Browse Source
This commit is contained in:
Hongli Lai (Phusion) 2013-11-12 12:55:16 +01:00
parent c214fffe46
commit fc32bf693d
No known key found for this signature in database
GPG Key ID: 06A131094B6F4332
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -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.