rancher/os
1
0
Fork 1
mirror of https://github.com/rancher/os.git synced 2025-07-13 06:34:04 +00:00
Code Issues Releases Wiki Activity
Mirror from github
2,339 Commits 23 Branches 183 Tags 80 MiB
Go 86.4%
Shell 12.7%
Dockerfile 0.4%
Smarty 0.3%
Makefile 0.2%
7d86fa5f8b
Go to file
Chris Marchesi 7d86fa5f8b
cmd/power: Another shutdown command fix 
It looks like some arguments for shutdown/halt/poweroff have been moved
to a conditional block that works off of how the command was actually
called. However, this value is derived from argv 0, without any sort of
normalization to make sure it matches the relative commands used to
determine how arguments are handled.

This has particular implications when power management commands are
called via absolute commands, as for example in the case of
open-vm-tools which calls /sbin/shutdown -h now specifically when
shutting down a system.

This corrects the situation by passing argv 0 through filepath.Base
before operating on it.
2018-03-06 14:16:44 -08:00
.github Update ISSUE_TEMPLATE.md 2016-05-05 22:12:07 -07:00
assets Remove dnspatch we have not used it anymore (#2198) 2017-12-29 15:20:43 +08:00
cmd cmd/power: Another shutdown command fix 2018-03-06 14:16:44 -08:00
compose Fix error typo in loadConsoleService func (#2112) 2017-12-07 15:55:40 +08:00
config Fix go test for ssh port and listen_address config 2018-03-05 16:39:30 +08:00
dfs Fix format 'verbs' (#2115) 2018-01-25 09:47:17 +08:00
docker Support higher verion docker-ce as system-docker 2018-02-27 23:44:22 +08:00
hostname Fix golint check error 2017-12-06 13:45:49 +08:00
images Fix for mtu display (#2209) 2018-01-05 17:34:36 +08:00
init Support higher verion docker-ce as system-docker 2018-02-27 23:44:22 +08:00
log Fix format 'verbs' (#2115) 2018-01-25 09:47:17 +08:00
netconf Get dhcp lease only for ipv4 2018-01-20 09:27:50 +08:00
scripts globalcfg: reboot 10s after kernel panic fixes #1785 (#1786) 2018-03-05 16:55:01 +08:00
selinux Move in code from netconf and docker-from-scratch 2016-10-19 16:21:35 -07:00
tests 17.06.1-ce is now in the repo 2017-08-29 12:03:39 +10:00
util Support URL when using ros install -c (#2202) 2018-01-02 17:17:43 +08:00
vendor Vendor changes for vishvananda/netlink 2017-12-19 17:49:56 +08:00
.dockerignore update master to generate docs like rancher.github.io does 2017-08-17 06:01:19 +10:00
.drone.yml Update for Drone 0.5 2016-08-28 12:16:21 -07:00
.gitignore Update ignore 2018-02-28 15:43:30 +08:00
Dockerfile.dapper Bump system-docker to 17.06-ros3 2018-03-05 13:32:00 +08:00
LICENSE Remove incorrect copyright 2015-02-25 10:22:56 -07:00
main.go Remove system-docker syslink 2018-02-27 23:44:22 +08:00
Makefile Add rancher.resize_device cmdline for DO 2018-03-01 09:35:45 +08:00
os-config.tpl.yml Config ROS image prefix for install and all rancher/os services (#2272) 2018-03-06 18:07:21 +08:00
rancheros.png Delete all the documents to ensure that they are maintained on github.rancher.io 2017-12-28 09:29:56 +08:00
README.md Update README for v1.2.0 release 2018-02-07 11:35:15 +08:00
trash.conf Vendor changes for vishvananda/netlink 2017-12-19 17:49:56 +08:00

README.md

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

Stable Release

v1.2.0 - Docker 17.09.1-ce - Linux 4.9.78

ISO

Additional Downloads

Latest Links

v1.2.0 Links

ARM Links

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

Amazon

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

HVM

Region Type AMI
ap-south-1 HVM ami-12db887d
eu-west-3 HVM ami-d5a315a8
eu-west-2 HVM ami-80bd58e7
eu-west-1 HVM ami-69187010
ap-northeast-2 HVM ami-57dd7f39
ap-northeast-1 HVM ami-a3c2b5c5
sa-east-1 HVM ami-6c2f6100
ca-central-1 HVM ami-b8a622dc
ap-southeast-1 HVM ami-0f5a1b73
ap-southeast-2 HVM ami-edc73c8f
eu-central-1 HVM ami-28422647
us-east-1 HVM ami-a7151cdd
us-east-2 HVM ami-a383b6c6
us-west-1 HVM ami-c4b3bca4
us-west-2 HVM ami-6e1a9e16

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

Google Compute Engine

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.

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.

For security issues, please email security@rancher.com 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.

License

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.