1
0
mirror of https://github.com/rancher/os.git synced 2025-08-10 11:03:16 +00:00
os/README.md

51 lines
1.5 KiB
Markdown
Raw Normal View History

2015-02-09 04:55:14 +00:00
# RancherOS
It's containers all the way down! Everything is powered by Docker (I mean everything).
## Building
2015-02-09 05:10:58 +00:00
Docker 1.5+ required.
2015-02-09 04:55:14 +00:00
./build.sh
## Running
2015-02-21 07:47:18 +00:00
KVM, VirtualBox, and VMware all supported (Clouds and Vagrant coming soon). Just
boot from the `rancheros.iso` from the [releases](https://github.com/rancherlabs/os/releases) page.
## Logging in
Log in with rancher/rancher and use `sudo` to get root access.
Once cloud-init integration is finished we will not need to hard code the
password anymore.
## Persisting State
Create a partition with the label `RANCHER_STATE`, for example
mkfs.ext4 -L RANCHER_STATE /dev/sda
## Configuring
The entire state of RancherOS is controlled by a single configuration document.
You can edit the configuration with the `rancherctl config` command.
2015-02-09 04:55:14 +00:00
## Commands
2015-02-09 05:10:58 +00:00
`docker` -- Good old Docker, use that to run stuff.
2015-02-21 07:47:18 +00:00
`system-docker` -- The docker instance running the system containers. Must run as root
`rancherctl` -- Control and configure RancherOS
## How does this work
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. We created this separation as is really seemed like a
bad idea that if somebody did `docker rm -f $(docker ps -qa)` they would delete the entire OS.
![How it works](https://raw.githubusercontent.com/rancherlabs/os/master/docs/rancheros.png "How it works")