From 99e5d08c276df8bdbc07c1dc154c6b4e9b233d52 Mon Sep 17 00:00:00 2001 From: Denise Date: Mon, 11 Apr 2016 09:32:51 -0700 Subject: [PATCH] Update README.md --- README.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 6219e0be..e63d0dc7 100644 --- a/README.md +++ b/README.md @@ -1,18 +1,15 @@ # RancherOS -The smallest, easiest way to run Docker in production at scale. Everything in RancherOS is a container managed by Docker. This includes system services such as udev and rsyslog. RancherOS includes only the bare minimum amount of software needed to run Docker. This keeps the binary download of RancherOS to about 25MB. Everything else can be pulled in dynamically through Docker. +The smallest, easiest way to run Docker in production at scale. Everything in RancherOS is a container managed by Docker. This includes system services such as udev and rsyslog. RancherOS includes only the bare minimum amount of software needed to run Docker. This keeps the binary download of RancherOS very small. Everything else can be pulled in dynamically through Docker. ## How this works Everything in RancherOS is a Docker container. We accomplish this by launching two instances of -Docker. One is what we call the system Docker which runs as PID 1. System Docker then launches +Docker. One is what we call the system Docker which runs as the first process. System Docker then launches a container that runs the user Docker. The user Docker is then the instance that gets primarily used to create containers. We created this separation because it seemed logical and also it would really be bad if somebody did `docker rm -f $(docker ps -qa)` and deleted the entire OS. -![How it works](docs/rancheros.png "How it works") - - ## Latest Release **v0.4.3 - Docker 1.10.1- Linux 4.2.8**