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.

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

v1.2.0 - Docker 17.09.1-ce - Linux 4.9.78

• https://releases.rancher.com/os/latest/rancheros.iso
• https://releases.rancher.com/os/v1.2.0/rancheros.iso

• https://releases.rancher.com/os/latest/initrd
• https://releases.rancher.com/os/latest/iso-checksums.txt
• https://releases.rancher.com/os/latest/rancheros-openstack.img
• https://releases.rancher.com/os/latest/rancheros-digitalocean.img
• https://releases.rancher.com/os/latest/rancheros-aliyun.vhd
• https://releases.rancher.com/os/latest/rancheros.ipxe
• https://releases.rancher.com/os/latest/rancheros-gce.tar.gz
• https://releases.rancher.com/os/latest/rootfs.tar.gz
• https://releases.rancher.com/os/latest/vmlinuz

• https://releases.rancher.com/os/v1.2.0/initrd
• https://releases.rancher.com/os/v1.2.0/iso-checksums.txt
• https://releases.rancher.com/os/v1.2.0/rancheros-openstack.img
• https://releases.rancher.com/os/v1.2.0/rancheros-digitalocean.img
• https://releases.rancher.com/os/v1.2.0/rancheros-aliyun.vhd
• https://releases.rancher.com/os/v1.2.0/rancheros.ipxe
• https://releases.rancher.com/os/v1.2.0/rancheros-gce.tar.gz
• https://releases.rancher.com/os/v1.2.0/rootfs.tar.gz
• https://releases.rancher.com/os/v1.2.0/vmlinuz

• https://releases.rancher.com/os/latest/rootfs_arm64.tar.gz
• https://releases.rancher.com/os/latest/rancheros-raspberry-pi64.zip
• https://releases.rancher.com/os/v1.2.0/rootfs_arm64.tar.gz
• https://releases.rancher.com/os/v1.2.0/rancheros-raspberry-pi64.zip

Note: you can use http instead of https in the above URLs, e.g. for iPXE.

SSH keys are added to the rancher user, so you must log in using the rancher user.

HVM

Additionally, images are available with support for Amazon EC2 Container Service (ECS) here.

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.

Download Image

Please follow the directions at our docs to launch in GCE.

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.

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.

For security issues, please email [email protected] instead of posting a public issue in GitHub. You may (but are not required to) use the GPG key located on Keybase.

Please submit any RancherOS bugs, issues, and feature requests to rancher/os.

Please submit any Rancher bugs, issues, and feature requests to rancher/rancher.

Copyright (c) 2014-2018 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.