mirror of
https://github.com/rancher/os.git
synced 2025-08-15 21:43:42 +00:00
more merges from rancher docs repo
Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
This commit is contained in:
Sven Dowideit
parent
daed587841
commit
c3a501d33d
@ -28,6 +28,9 @@ For the **User Data**, you'll need to pass in the [cloud-config]({{site.baseurl}
|
||||
rancher:
|
||||
environment:
|
||||
ECS_CLUSTER: your-ecs-cluster-name
|
||||
# Note: You will need to add this variable, if using awslogs for ECS task.
|
||||
ECS_AVAILABLE_LOGGING_DRIVERS: |-
|
||||
["json-file","awslogs"]
|
||||
# If you have selected a RancherOS AMI that does not have ECS enabled by default,
|
||||
# you'll need to enable the system service for the ECS agent.
|
||||
services_include:
|
||||
|
||||
@ -5,12 +5,13 @@ layout: os-default
|
||||
---
|
||||
|
||||
## Configuring Docker or System Docker
|
||||
---
|
||||
|
||||
In RancherOS, you can configure System Docker and Docker daemons by using [cloud-config]({{site.baseurl}}/os/configuration/#cloud-config).
|
||||
In RancherOS, you can configure System Docker and Docker daemons by using [cloud-config]({{site.baseurl}}/os/configuration/#cloud-config).
|
||||
|
||||
### Configuring Docker
|
||||
|
||||
In your cloud-config, Docker configuration is located under the `rancher.docker` key.
|
||||
In your cloud-config, Docker configuration is located under the `rancher.docker` key.
|
||||
|
||||
```yaml
|
||||
#cloud-config
|
||||
@ -19,7 +20,7 @@ rancher:
|
||||
tls: true
|
||||
tls_args: [--tlsverify, --tlscacert=ca.pem, --tlscert=server-cert.pem, --tlskey=server-key.pem, '-H=0.0.0.0:2376']
|
||||
storage_driver: overlay
|
||||
```
|
||||
```
|
||||
|
||||
You can also customize Docker after it's been started using `ros config`.
|
||||
|
||||
@ -57,17 +58,17 @@ In addition to the standard daemon arguments, there are a few fields specific to
|
||||
Key | Value | Default | Description
|
||||
---|---|---| ---
|
||||
`extra_args` | List of Strings | `[]` | Arbitrary daemon arguments, appended to the generated command
|
||||
`environment` | List of Strings | `[]` |
|
||||
`environment` | List of Strings | `[]` |
|
||||
`tls` | Boolean | `false` | When [setting up TLS]({{site.baseurl}}/os/configuration/setting-up-docker-tls/), this key needs to be set to true.
|
||||
`tls_args` | List of Strings (used only if `tls: true`) | `[]` |
|
||||
`server_key` | String (used only if `tls: true`)| `""` | PEM encoded server TLS key.
|
||||
`tls_args` | List of Strings (used only if `tls: true`) | `[]` |
|
||||
`server_key` | String (used only if `tls: true`)| `""` | PEM encoded server TLS key.
|
||||
`server_cert` | String (used only if `tls: true`) | `""` | PEM encoded server TLS certificate.
|
||||
`ca_key` | String (used only if `tls: true`) | `""` | PEM encoded CA TLS key.
|
||||
`ca_key` | String (used only if `tls: true`) | `""` | PEM encoded CA TLS key.
|
||||
`storage_context` | String | `console` | Specifies the name of the system container in whose context to run the Docker daemon process.
|
||||
|
||||
### Configuring System Docker
|
||||
|
||||
In your cloud-config, System Docker configuration is located under the `rancher.system_docker` key.
|
||||
In your cloud-config, System Docker configuration is located under the `rancher.system_docker` key.
|
||||
|
||||
```yaml
|
||||
#cloud-config
|
||||
@ -83,4 +84,4 @@ All daemon arguments shown in the first table are also available to System Docke
|
||||
Key | Value | Default | Description
|
||||
---|---|---| ---
|
||||
`extra_args` | List of Strings | `[]` | Arbitrary daemon arguments, appended to the generated command
|
||||
`environment` | List of Strings (optional) | `[]` |
|
||||
`environment` | List of Strings (optional) | `[]` |
|
||||
|
||||
@ -5,13 +5,14 @@ layout: os-default
|
||||
---
|
||||
|
||||
## Installing Kernel Modules that require Kernel Headers
|
||||
---
|
||||
|
||||
|
||||
To compile any kernel modules, you will need to download the kernel headers. The kernel headers are available in the form of a system service. Since the kernel headers are a system service, they need to be enabled using the `ros service` command.
|
||||
To compile any kernel modules, you will need to download the kernel headers. The kernel headers are available in the form of a system service. Since the kernel headers are a system service, they need to be enabled using the `ros service` command.
|
||||
|
||||
### Installing Kernel Headers
|
||||
|
||||
The following commands can be used to install kernel headers for usage by containers in Docker or System Docker.
|
||||
The following commands can be used to install kernel headers for usage by containers in Docker or System Docker.
|
||||
|
||||
#### Docker
|
||||
|
||||
@ -29,13 +30,13 @@ $ sudo ros service up kernel-headers-system-docker
|
||||
|
||||
The `ros service` commands will install the kernel headers in `/lib/modules/$(uname -r)/build`. Based on which service you install, the kernel headers will be available to containers, in Docker or System Docker, by bind mounting specific volumes. For any containers that compile a kernel module, the Docker command will need to bind mount in `/usr/src` and `/lib/modules`.
|
||||
|
||||
> **Note:** Since both commands install kernel headers in the same location, the only reason for different services is due to the fact that the storage places for System Docker and Docker are different. Either one or both kernel headers can be installed in the same RancherOS services.
|
||||
> **Note:** Since both commands install kernel headers in the same location, the only reason for different services is due to the fact that the storage places for System Docker and Docker are different. Either one or both kernel headers can be installed in the same RancherOS services.
|
||||
|
||||
### Example of Launching Containers to use Kernel Headers
|
||||
|
||||
```
|
||||
# Run a container in Docker and bind mount specific directories
|
||||
$ docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10
|
||||
# Run a container in System Docker and bind mount specific directories
|
||||
$ sudo system-docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10
|
||||
# Run a container in Docker and bind mount specific directories
|
||||
$ docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10
|
||||
# Run a container in System Docker and bind mount specific directories
|
||||
$ sudo system-docker run -it -v /usr/src:/usr/src -v /lib/modules:/lib/modules ubuntu:15.10
|
||||
```
|
||||
|
||||
@ -76,3 +76,25 @@ If you don't want to automatically switch Docker engines, you can also set which
|
||||
```
|
||||
$ sudo ros engine enable docker-1.10.3
|
||||
```
|
||||
|
||||
## Using a Custom Version of Docker
|
||||
|
||||
If you're using a version of Docker that isn't available by default or a custom build of Docker then you can create a custom Docker image and service file to distribute it.
|
||||
|
||||
Docker engine images are built by adding the binaries to a folder named `engine` and then adding this folder to a `FROM scratch` image. For example, the following Dockerfile will build a Docker engine image.
|
||||
|
||||
```
|
||||
FROM scratch
|
||||
COPY engine /engine
|
||||
```
|
||||
|
||||
Once the image is built a [system service]({{site.baseurl}}/os/system-services/adding-system-services/) configuration file must be created. An [example file](https://github.com/rancher/os-services/blob/master/d/docker-1.12.3.yml) can be found in the rancher/os-services repo. Change the `image` field to point to the Docker engine image you've built.
|
||||
|
||||
All of the previously mentioned methods of switching Docker engines are now available. For example, if your service file is located at `https://myservicefile` then the following cloud-config file could be used to use your custom Docker engine.
|
||||
|
||||
```yaml
|
||||
#cloud-config
|
||||
rancher:
|
||||
docker:
|
||||
engine: https://myservicefile
|
||||
```
|
||||
|
||||
@ -5,9 +5,9 @@ layout: os-default
|
||||
|
||||
## Overview of RancherOS
|
||||
---
|
||||
RancherOS is the smallest, easiest way to run Docker in production. Everything in RancherOS is a container managed by Docker. This includes system services such as `udev` and `syslog`. RancherOS is dramatically smaller than most traditional operating systems, because it only includes the services necessary to run Docker. By removing unnecessary libraries and services, requirements for security patches and other maintenance are dramatically reduced. This is possible because with Docker, users typically package all necessary libraries into their containers.
|
||||
RancherOS is the smallest, easiest way to run Docker in production. Everything in RancherOS is a container managed by Docker. This includes system services such as `udev` and `syslog`. RancherOS is dramatically smaller than most traditional operating systems, because it only includes the services necessary to run Docker. By removing unnecessary libraries and services, requirements for security patches and other maintenance are dramatically reduced. This is possible because with Docker, users typically package all necessary libraries into their containers.
|
||||
|
||||
Another way in which RancherOS is designed specifically for running Docker is that it always runs the latest version of Docker. This allows users to take advantage of the latest Docker capabilities and bug fixes.
|
||||
Another way in which RancherOS is designed specifically for running Docker is that it always runs the latest version of Docker. This allows users to take advantage of the latest Docker capabilities and bug fixes.
|
||||
|
||||
Like other minimalist Linux distributions, RancherOS boots incredibly quickly, generally in 5-10 seconds. Starting Docker containers is nearly instant, similar to starting any other process. This quickness is ideal for organizations adopting microservices and autoscaling.
|
||||
|
||||
@ -18,7 +18,7 @@ Docker is an open-source platform designed for developers, system admins, and De
|
||||
|
||||
* x86_64 server with at least 512MB of RAM.
|
||||
|
||||
> **Note:** If you are planning on [installing to disk]({{site.baseurl}}/os/running-rancheros/server/install-to-disk/), you will need at least 1024MB of RAM.
|
||||
> **Note:** If you are planning on [installing to disk]({{site.baseurl}}/os/running-rancheros/server/install-to-disk/), you will need at least 1024MB of RAM.
|
||||
|
||||
|
||||
### How this works
|
||||
@ -28,7 +28,7 @@ Everything in RancherOS is a Docker container. We accomplish this by launching t
|
||||
|
||||
System Docker runs a special container called **Docker**, which is another Docker daemon responsible for managing all of the user’s containers. Any containers that you launch as a user from the console will run inside this Docker. This creates isolation from the System Docker containers, and ensures normal user commands don’t impact system services.
|
||||
|
||||
We created this separation because it seemed logical and also it would really be bad if somebody did
|
||||
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.
|
||||
|
||||
|
||||
@ -39,7 +39,7 @@ To find out more about installing RancherOS, jump to our [Quick Start Guide]({{s
|
||||
|
||||
### Latest Release
|
||||
---
|
||||
Please check our repository for the latest release in our [README](https://github.com/rancher/os/blob/master/README.md).
|
||||
Please check our repository for the latest release in our [README](https://github.com/rancher/os/blob/master/README.md).
|
||||
|
||||
<br>
|
||||
<br>
|
||||
|
||||
@ -6,6 +6,7 @@ redirect_from:
|
||||
---
|
||||
|
||||
## Interfaces
|
||||
---
|
||||
|
||||
Using `ros config`, you can configure specific interfaces. Wildcard globbing is supported so `eth*` will match `eth1` and `eth2`. The available options you can configure are `address`, `gateway`, `mtu`, and `dhcp`.
|
||||
|
||||
@ -94,3 +95,19 @@ rancher:
|
||||
eth0:
|
||||
vlans: 100,200:foobar
|
||||
```
|
||||
|
||||
### Bridging
|
||||
|
||||
In this example, you can create a bridge interface.
|
||||
|
||||
```
|
||||
#cloud-config
|
||||
rancher:
|
||||
network:
|
||||
interfaces:
|
||||
br0:
|
||||
bridge: true
|
||||
dhcp: true
|
||||
eth0:
|
||||
bridge: br0
|
||||
```
|
||||
|
||||
@ -11,7 +11,7 @@ If you have a specific RanchersOS machine requirements, please check out our [gu
|
||||
|
||||
### Launching RancherOS using Docker Machine
|
||||
|
||||
Before moving forward, you'll need to have [Docker Machine](https://docs.docker.com/machine/) and [VirtualBox](https://www.virtualbox.org/wiki/Downloads) installed. Once you have VirtualBox and Docker Machine installed, it's just one command to get RancherOS running.
|
||||
Before moving forward, you'll need to have [Docker Machine](https://docs.docker.com/machine/) and [VirtualBox](https://www.virtualbox.org/wiki/Downloads) installed. Once you have VirtualBox and Docker Machine installed, it's just one command to get RancherOS running.
|
||||
|
||||
```
|
||||
$ docker-machine create -d virtualbox --virtualbox-boot2docker-url https://releases.rancher.com/os/latest/rancheros.iso <MACHINE-NAME>
|
||||
@ -27,11 +27,11 @@ $ docker-machine ssh <MACHINE-NAME>
|
||||
|
||||
### A First Look At RancherOS
|
||||
|
||||
There are two Docker daemons running in RancherOS. The first is called **System Docker**, which is where RancherOS runs system services like ntpd and syslog. You can use the `system-docker` command to control the **System Docker** daemon.
|
||||
There are two Docker daemons running in RancherOS. The first is called **System Docker**, which is where RancherOS runs system services like ntpd and syslog. You can use the `system-docker` command to control the **System Docker** daemon.
|
||||
|
||||
The other Docker daemon running on the system is **Docker**, which can be accessed by using the normal `docker` command.
|
||||
|
||||
When you first launch RancherOS, there are no containers running in the Docker daemon. However, if you run the same command against the System Docker, you’ll see a number of system services that are shipped with RancherOS.
|
||||
When you first launch RancherOS, there are no containers running in the Docker daemon. However, if you run the same command against the System Docker, you’ll see a number of system services that are shipped with RancherOS.
|
||||
|
||||
> **Note:** `system-docker` can only be used by root, so it is necessary to use the `sudo` command whenever you want to interact with System Docker.
|
||||
|
||||
@ -57,7 +57,7 @@ Some containers are run at boot time, and others, such as the `console`, `docker
|
||||
Let's try to deploy a normal Docker container on the Docker daemon. The RancherOS Docker daemon is identical to any other Docker environment, so all normal Docker commands work.
|
||||
|
||||
```
|
||||
$ docker run -d nginx
|
||||
$ docker run -d nginx
|
||||
```
|
||||
|
||||
You can see that the nginx container is up and running:
|
||||
@ -106,7 +106,7 @@ $ sudo chmod 755 /opt/rancher/bin/start.sh
|
||||
|
||||
### Using ROS
|
||||
|
||||
Another useful command that can be used with RancherOS is `ros` which can be used to control and configure the system.
|
||||
Another useful command that can be used with RancherOS is `ros` which can be used to control and configure the system.
|
||||
|
||||
```
|
||||
$ ros -v
|
||||
@ -130,5 +130,5 @@ $ sudo ros console switch ubuntu
|
||||
|
||||
### Conclusion
|
||||
|
||||
RancherOS is a simple Linux distribution ideal for running Docker. By embracing containerization of system services and leveraging Docker for management, RancherOS hopes to provide a very reliable, and easy to manage OS for running containers.
|
||||
RancherOS is a simple Linux distribution ideal for running Docker. By embracing containerization of system services and leveraging Docker for management, RancherOS hopes to provide a very reliable, and easy to manage OS for running containers.
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ layout: os-default
|
||||
---
|
||||
## Running RancherOS on AWS
|
||||
----
|
||||
RancherOS is available as an Amazon Web Services AMI, and can be easily run on EC2. You can launch RancherOS either using the AWS Command Line Interface (CLI) or using the AWS console.
|
||||
RancherOS is available as an Amazon Web Services AMI, and can be easily run on EC2. You can launch RancherOS either using the AWS Command Line Interface (CLI) or using the AWS console.
|
||||
|
||||
### Launching RancherOS through the AWS CLI
|
||||
|
||||
@ -13,7 +13,7 @@ If you haven't installed the AWS CLI, follow the instructions on the [AWS CLI pa
|
||||
|
||||
Once you've installed your AWS CLI, use this command to launch an EC2 instance with the RancherOS AMI. You will need to know your SSH key name and security group name for the _region_ that you are configured for. These can be found from the AWS console.
|
||||
|
||||
> **Note:** Check the RancherOS [README](https://github.com/rancher/os/blob/master/README.md) for AMI names for each region. We support PV and HVM types of AMIs.
|
||||
> **Note:** Check the RancherOS [README](https://github.com/rancher/os/blob/master/README.md) for AMI names for each region. We support PV and HVM types of AMIs.
|
||||
|
||||
```
|
||||
$ aws ec2 run-instances --image-id ami-ID# --count 1 --instance-type t2.micro --key-name MySSHKeyName --security-groups sg-name
|
||||
@ -34,20 +34,20 @@ Let’s walk through how to import and create a RancherOS on EC2 machine using t
|
||||
|
||||
|
||||
|
||||
3. Go through the steps of creating the instance type through the AWS console. If you want to pass in a [cloud-config]({{site.baseurl}}/os/configuration/#cloud-config) file during boot of RancherOS, you'd pass in the file as **User data** by expanding the **Advanced Details** in **Step 3: Configure Instance Details**. You can pass in the data as text or as a file.
|
||||
|
||||
3. Go through the steps of creating the instance type through the AWS console. If you want to pass in a [cloud-config]({{site.baseurl}}/os/configuration/#cloud-config) file during boot of RancherOS, you'd pass in the file as **User data** by expanding the **Advanced Details** in **Step 3: Configure Instance Details**. You can pass in the data as text or as a file.
|
||||
|
||||
|
||||
|
||||
After going through all the steps, you finally click on **Launch**, and either create a new key pair or choose an existing key pair to be used with the EC2 instance. If you have created a new key pair, download the key pair. If you have chosen an existing key pair, make sure you have the key pair accessible. Click on **Launch Instances**.
|
||||
After going through all the steps, you finally click on **Launch**, and either create a new key pair or choose an existing key pair to be used with the EC2 instance. If you have created a new key pair, download the key pair. If you have chosen an existing key pair, make sure you have the key pair accessible. Click on **Launch Instances**.
|
||||
|
||||
|
||||
|
||||
4. Your instance will be launching and you can click on **View Instances** to see it's status.
|
||||
|
||||
|
||||
|
||||
|
||||
Your instance is now running!
|
||||
|
||||
|
||||
|
||||
|
||||
## Logging into RancherOS
|
||||
@ -66,7 +66,7 @@ If you have issues logging into RancherOS, try using this command to help debug
|
||||
$ ssh -v -i /Directory/of/MySSHKeyName.pem rancher@<ip-of-ec2-instance>
|
||||
```
|
||||
|
||||
## Latest AMI Releases
|
||||
## Latest AMI Releases
|
||||
----
|
||||
|
||||
Please check the [README](https://github.com/rancher/os/blob/master/README.md) in our RancherOS repository for our latest AMIs.
|
||||
|
||||
@ -16,7 +16,7 @@ RancherOS is available as an image in GCE, and can be easily run in Google Compu
|
||||
|
||||
2. Follow Google's instructions on how to [upload the image](https://cloud.google.com/compute/docs/tutorials/building-images#publishingimage). The image must be uploaded into a Google Cloud Storage bucket before it can be added to a project.
|
||||
|
||||
3. Follow Google's instructions on how to [import a RAW image](https://cloud.google.com/compute/docs/images/import-existing-image#use_saved_image).
|
||||
3. Follow Google's instructions on how to [import a RAW image](https://cloud.google.com/compute/docs/images/import-existing-image#use_saved_image).
|
||||
|
||||
4. Once the image is added to your Google Compute Engine, we can start creating new instances!
|
||||
|
||||
|
||||
@ -12,6 +12,8 @@ When installing, there is no ability to pass in a [cloud-config]({{site.baseurl}
|
||||
|
||||
Currently, only Raspberry Pi 2 and 3 are tested and known to work.
|
||||
|
||||
> **Note:** It is not necessary to run `ros install` after installing RancherOS to an SD card.
|
||||
|
||||
### Using the entire SD Card
|
||||
|
||||
RancherOS does not currently expand the root partition to fill the remainder of the SD card automatically. Instead, the following workaround can be used to store Docker containers on a larger partition that fills the remainder.
|
||||
|
||||
@ -9,7 +9,7 @@ The RancherOS ISO file can be used to create a fresh RancherOS install on KVM, V
|
||||
|
||||
You must boot with at least **512MB** of memory. If you boot with the ISO, you will automatically be logged in as the `rancher` user. Only the ISO is set to use autologin by default. If you run from a cloud or install to disk, SSH keys or a password of your choice is expected to be used.
|
||||
|
||||
> **Note:** If you are planning on [installing to disk]({{site.baseurl}}/os/running-rancheros/server/install-to-disk/), you will need at least 1.5GB of RAM.
|
||||
> **Note:** If you are planning on [installing to disk]({{site.baseurl}}/os/running-rancheros/server/install-to-disk/), you will need at least 1.5GB of RAM.
|
||||
|
||||
### Install to Disk
|
||||
---
|
||||
@ -17,7 +17,7 @@ After you boot RancherOS from ISO, you can follow the instructions [here]({{site
|
||||
|
||||
### Persisting State
|
||||
---
|
||||
If you are running from the ISO, RancherOS will be running from memory. All downloaded Docker images, for example, will be stored in a ramdisk and will be lost after the server is rebooted. You can
|
||||
If you are running from the ISO, RancherOS will be running from memory. All downloaded Docker images, for example, will be stored in a ramdisk and will be lost after the server is rebooted. You can
|
||||
create a file system with the label `RANCHER_STATE` to instruct RancherOS to use that partition to store state. Suppose you have a disk partition on the server called `/dev/sda`, the following command formats that partition and labels it `RANCHER_STATE`
|
||||
|
||||
```
|
||||
@ -38,13 +38,13 @@ After you reboot, the server RancherOS will use `/dev/sda` as the state partitio
|
||||
1. Download the RancherOS ISO.
|
||||
|
||||
2. Start up a VM from VirtualBox.
|
||||
|
||||
|
||||
a. Open up VirtualBox. If you don't have VirtualBox, download it [here](https://www.virtualbox.org/wiki/Downloads).
|
||||
|
||||
|
||||
|
||||
b. Provide a **name**, select the **type** to be _Linux_, and select the **version** to be _Other Linux (64-bit)_. Click **Continue**.
|
||||
|
||||
|
||||
|
||||
|
||||
c. Select at least **1GB** of RAM.
|
||||
@ -61,24 +61,24 @@ After you reboot, the server RancherOS will use `/dev/sda` as the state partitio
|
||||
|
||||
f. Select **Dynamically allocated** and click **Continue**.
|
||||
|
||||
|
||||
|
||||
|
||||
g. Click **Create**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Your new VM should be created, but in a _Powered Off_ state.
|
||||
|
||||
3. Start the VM from VirtualBox by clicking on the VM and clicking **Start** or right-click on the box and select **Start**. You will be immediately prompted to select an ISO. Find the RancherOS ISO that you have downloaded. Click **Start**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. When RancherOS launches, you will be prompted for a rancher login and password. The login and password is 'rancher' (all lowercase).
|
||||
|
||||
```
|
||||
RancherOS rancher /dev/ttyl
|
||||
rancher login: rancher
|
||||
Password:
|
||||
Password:
|
||||
```
|
||||
|
||||
Next, read about how to [install to disk]({{site.baseurl}}/os/running-rancheros/server/install-to-disk/) in order to have any changes to RancherOS to be saved.
|
||||
|
||||
@ -4,6 +4,7 @@ layout: os-default
|
||||
---
|
||||
|
||||
## Persistent State Partition
|
||||
---
|
||||
|
||||
RancherOS will store its state in a single partition specified by the `dev` field. The field can be a device such as `/dev/sda1` or a logical name such `LABEL=state` or `UUID=123124`. The default value is `LABEL=RANCHER_STATE`. The file system type of that partition can be set to `auto` or a specific file system type such as `ext4`.
|
||||
|
||||
|
||||
@ -6,6 +6,7 @@ redirect_from:
|
||||
---
|
||||
|
||||
## Using ZFS
|
||||
---
|
||||
|
||||
#### Installing the ZFS service
|
||||
|
||||
|
||||
@ -7,6 +7,7 @@ redirect_from:
|
||||
---
|
||||
|
||||
## System Services
|
||||
---
|
||||
|
||||
A system service is a container that can be run in either System Docker or Docker. Rancher provides services that are already available in RancherOS by adding them to the [os-services repo](https://github.com/rancher/os-services). Anything in the `index.yml` file from the repository for the tagged release will be an available system service when using the `ros service list` command.
|
||||
|
||||
|
||||
@ -13,6 +13,9 @@ Since RancherOS is a kernel and initrd, the upgrade process is downloading a new
|
||||
|
||||
To see all of our releases, please visit our [releases page](https://github.com/rancher/os/releases) in GitHub.
|
||||
|
||||
> **Note:** If you are using [`docker-machine`]({{site.baseurl}}/os/running-rancheros/workstation/docker-machine/) then you will not be able to upgrade your RancherOS version. You need to delete and re-create the machine.
|
||||
|
||||
|
||||
### Version Control
|
||||
|
||||
First, let's check what version you have running on your system.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user