rancher/os
1
0
Fork 1
mirror of https://github.com/rancher/os.git synced 2025-07-02 09:41:47 +00:00
Code Issues Releases Wiki Activity
Mirror from github
2,255 Commits 23 Branches 183 Tags 80 MiB
Go 86.4%
Shell 12.7%
Dockerfile 0.4%
Smarty 0.3%
Makefile 0.2%
2f8eaa3314
Go to file
Chris Marchesi 2f8eaa3314
cmd/power: Set correct container name and ensure full command executed 
This fixes a few issues that are preventing shutdown and friends from
behaving correctly:

* The command name, which is being used to determine via what command it
was being called (ie: shutdown, reboot, or halt) was not being parsed
for absolute paths. This was preventing certain logic from being handled
(example: enforcing a static time value of "now" for shutdown), but more
problematically was the fact that it was being used as the container
name being passed to runDocker, the function that launches the
independent shutdown container. This was causing the shutdown container
to fail as something like "/sbin/shutdown" is not a valid name for a
container. The logic to parse out the base command being run is actually
present in runDocker, but does not run if a name is supplied to the
function.

* Further, the command line was not being parsed in the shutdown
container if the name supplied to runDocker was non-empty. Rather, the
full command to run just became the name of the container. Hence,
something like "/sbin/shutdown -h now" became just "shutdown", executing
the default power off behaviour for all actions (including reboots).

* Further to this, open-vm-tools expects "/sbin/shutdown -h now" to be a
valid command to halt the system, which was not being recognized as the
only recognized short-form halt flag in shutdown was its capital version
(-H).

This fixes these three issues by parsing out the base of the called
command before sending it to reboot, using all of os.Argv as the command
line to run regardless of if a name was set for the container or not,
and finally adding the lowercase -h switch to the "shutdown" form of
this command ("halt" is still uppercase only).

Fixes rancher/os#2121.
Fixes rancher/os#2074.
2017-10-20 17:09:13 -07:00
.github Update ISSUE_TEMPLATE.md 2016-05-05 22:12:07 -07:00
assets Bump Go to 1.7.1 2016-09-15 22:03:17 -07:00
cmd cmd/power: Set correct container name and ensure full command executed 2017-10-20 17:09:13 -07:00
compose cache the user/system client if its created 2017-07-21 09:50:31 +10:00
config Refactor a little so 'ros os list' also uses the configured proxy info 2017-09-15 13:47:21 +10:00
dfs Stop overwriting a good resolv.conf file with the default one 2017-08-29 10:10:47 +10:00
docker Don't pull an image that is already local 2017-07-20 22:39:37 +10:00
docs we don't use DKMS anymore 2017-09-18 13:35:48 +10:00
hostname Move default hostname and network under common key 2016-05-31 22:27:04 -07:00
images add alog rotate for the dhcpcd.debug.log file 2017-09-12 21:07:43 +10:00
init set the http_proxy env vars for the consoles 2017-09-15 23:38:15 +10:00
log Stop overwriting a good resolv.conf file with the default one 2017-08-29 10:10:47 +10:00
netconf Stop overwriting a good resolv.conf file with the default one 2017-08-29 10:10:47 +10:00
scripts rpi64 linux kernel 4.9.50 2017-09-16 12:42:37 +00: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 set the http_proxy env vars for the consoles 2017-09-15 23:38:15 +10:00
vendor Fix validation tests, update deps and use the rancher/docker version that uses logrus for daemon 2017-07-17 23:03:09 +10: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 Updating documentation around kernel modules 2016-12-16 19:29:19 -06:00
Dockerfile.dapper linux kernel 4.9.49 2017-09-12 11:23:50 +10:00
LICENSE Remove incorrect copyright 2015-02-25 10:22:56 -07:00
main.go Make the bootstrap phase logable 2017-09-13 16:13:15 +10:00
Makefile 17.06.1-ce is now in the repo 2017-08-29 12:03:39 +10:00
os-config.tpl.yml Merge pull request #2104 from SvenDowideit/http-proxy-fix 2017-09-18 15:43:38 +10:00
README.md update version numbers and AMIs 2017-08-30 13:48:01 +10:00
trash.conf Fix validation tests, update deps and use the rancher/docker version that uses logrus for daemon 2017-07-17 23:03:09 +10: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

Latest Release

v1.1.0 - Docker 17.03.2-ce - Linux 4.9.45

ISO

Additional Downloads

Latest Links

v1.1.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-7145011e
eu-west-2 HVM ami-2dc0d049
eu-west-1 HVM ami-6b2cd712
ap-northeast-2 HVM ami-c2568eac
ap-northeast-1 HVM ami-14d72f72
sa-east-1 HVM ami-88087be4
ca-central-1 HVM ami-0f3a846b
ap-southeast-1 HVM ami-4866042b
ap-southeast-2 HVM ami-74aeb417
eu-central-1 HVM ami-1c339973
us-east-1 HVM ami-22cec059
us-east-1 HVM ami-62000e19
us-east-2 HVM ami-efd4f78a
us-west-1 HVM ami-964175f6
us-west-1 HVM ami-9c5b6ffc
us-west-2 HVM ami-9515feed

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