|
|
||
|---|---|---|
| assets | ||
| cmd | ||
| compose | ||
| config | ||
| docker | ||
| docs | ||
| init | ||
| scripts | ||
| selinux | ||
| tests/integration | ||
| util | ||
| vendor | ||
| .docker-env.sample | ||
| .dockerignore | ||
| .dockerignore.dapper | ||
| .drone.yml | ||
| .gitignore | ||
| .package | ||
| build.conf | ||
| build.conf.amd64 | ||
| build.conf.arm | ||
| build.conf.arm64 | ||
| build.sh | ||
| Dockerfile.amd64 | ||
| Dockerfile.arm64 | ||
| Dockerfile.dapper | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| os-config.tpl.yml | ||
| README.md | ||
| trash.yml | ||
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.
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.
Latest Release
v0.4.3 - Docker 1.10.1- Linux 4.2.8
ISO
https://releases.rancher.com/os/latest/rancheros.iso
https://releases.rancher.com/os/v0.4.3/rancheros.iso
Note: you must login using rancher for username and password.
Additional Downloads
-
https://releases.rancher.com/os/latest/rancheros-v0.4.3.tar.gz
-
https://releases.rancher.com/os/v0.4.3/rancheros-v0.4.3.tar.gz
Note: you can use http instead of https in the above URLs, e.g. for iPXE.
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.
HVM
| Region | Type | AMI |
|---|---|---|
| ap-northeast-1 | HVM | ami-58dbdd36 |
| ap-southeast-1 | HVM | ami-217eb042 |
| ap-southeast-2 | HVM | ami-8da483ee |
| eu-central-1 | HVM | ami-62b0ab0e |
| eu-west-1 | HVM | ami-7de95b0e |
| sa-east-1 | HVM | ami-70bc3f1c |
| us-east-1 | HVM | ami-6f023505 |
| us-west-1 | HVM | ami-17780977 |
| us-west-2 | HVM | ami-e45fbf84 |
Paravirtual
| Region | Type | AMI |
|---|---|---|
| ap-northeast-1 | PV | ami-c9d8dea7 |
| ap-southeast-1 | PV | ami-727cb211 |
| ap-southeast-2 | PV | ami-faa18699 |
| eu-central-1 | PV | ami-11b5ae7d |
| eu-west-1 | PV | ami-8fe755fc |
| sa-east-1 | PV | ami-9b4ac9f7 |
| us-east-1 | PV | ami-b70136dd |
| us-west-1 | PV | ami-4a7a0b2a |
| us-west-2 | PV | ami-d0a340b0 |
Google Compute Engine (Experimental)
We are providing a disk image that users can download and import for use in Google Compute Engine. The image can be obtained from the release artifacts for RancherOS v0.3.0 or later.
Please follow the directions at our docs to launch in GCE.
Known issues/ToDos
- Add GCE daemon support. (Manages users)
Documentation for RancherOS
Please refer to our RancherOS Documentation website to read all about RancherOS. It has detailed information on how RancherOS works, getting-started and other details.
Support, Discussion, and Community
If you need any help with RancherOS or Rancher, please join us at either our Rancher forums or #rancher IRC channel where most of our team hangs out at.
Please submit any RancherOS bugs, issues, and feature requests to rancher/os.
Please submit any Rancher bugs, issues, and feature requests to rancher/rancher.
#License Copyright (c) 2014-2016 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.