1
0
mirror of https://github.com/rancher/os.git synced 2025-07-19 17:39:04 +00:00
Mirror from github
Go to file
2015-04-20 13:24:22 -07:00
assets Fix more issues with state management 2015-02-16 22:27:32 -07:00
cmd Properly marshall #compose and script files in cloud-config.d 2015-04-17 06:37:56 -07:00
config Remove trailing / 2015-04-16 07:26:42 -07:00
docker Remove commented code 2015-04-17 06:37:56 -07:00
docs Update rancherctl-tls.md 2015-04-07 09:40:41 -07:00
Godeps Godep updates 2015-04-15 23:17:01 -07:00
init Services in compose format 2015-04-15 23:17:01 -07:00
scripts bump v0.3.0 2015-04-18 23:17:41 -07:00
util Change log level 2015-04-17 06:37:56 -07:00
.dockerignore Update ignores 2015-03-18 06:45:21 -07:00
.drone.yml CI scripts 2015-02-17 17:01:38 -07:00
.gitignore Update ignores 2015-03-18 06:45:21 -07:00
.package Initial commit 2015-02-08 21:38:37 -07:00
.wrap-docker-args Initial commit 2015-02-08 21:38:37 -07:00
build.sh Dynamically set version for ubuntu console 2015-03-20 12:43:24 -07:00
GETTING_STARTED.md Update GETTING_STARTED.md 2015-03-05 00:05:30 +02:00
LICENSE Remove incorrect copyright 2015-02-25 10:22:56 -07:00
main.go Wait for userdocker to start 2015-04-04 09:55:41 -07:00
README.md Update README.md 2015-04-20 12:20:36 -07:00

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 20MB. 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 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

Latest Release

v0.3.0 - Docker 1.6.0 - Linux 3.19.2

ISO

https://github.com/rancherio/os/releases/download/v0.3.0/rancheros.iso

Amazon

We have 2 different virtualization types of AMIs. SSH keys are added to the rancher user, so you must log in using the rancher user.

Paravirtual

Region Type AMI
ap-northeast-1 PV ami-506da950
ap-southeast-1 PV ami-14043946
ap-southeast-2 PV ami-37acd10d
eu-west-1 PV ami-2d8fec5a
sa-east-1 PV ami-fd7ffae0
us-east-1 PV ami-ca3e39a2
us-west-1 PV ami-55816c11
us-west-2 PV ami-29c1f419

HVM

Region Type AMI
ap-northeast-1 PV ami-be6da9be
ap-southeast-1 PV ami-06043954
ap-southeast-2 PV ami-23acd119
eu-west-1 PV ami-018fec76
sa-east-1 PV ami-f17ffaec
us-east-1 PV ami-b03e39d8
us-west-1 PV ami-6d816c29
us-west-2 PV ami-1fc1f42f

Documentation for Rancher Labs

Please refer to our website to read all about RancherOS. It has detailed information on how it works, getting-started and other details.

#License Copyright (c) 2014-2015 Rancher Labs, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.