mirror of
https://github.com/rancher/os.git
synced 2025-09-09 02:31:36 +00:00
Merge pull request #1983 from SvenDowideit/sync-docs-1407
Sync docs changes
This commit is contained in:
@@ -5,7 +5,7 @@
|
||||
<title>{{ page.title }}</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="{{ site.description }}">
|
||||
<link href="/favicon.png" rel="shortcut icon" type="image/png" sizes="16x16">
|
||||
<link href="{{site.baseurl}}/favicon.png" rel="shortcut icon" type="image/png" sizes="16x16">
|
||||
<link href="{{site.baseurl}}/css/syntax.css?t={{site.time}}" rel="stylesheet">
|
||||
<link href="{{site.baseurl}}/vendor/font-awesome/css/font-awesome.min.css?t={{site.time}}" rel="stylesheet">
|
||||
<link href="{{site.baseurl}}/vendor/lato/lato.css?t={{site.time}}" rel="stylesheet">
|
||||
|
@@ -1,11 +1,12 @@
|
||||
---
|
||||
title: Overview of RancherOS
|
||||
title: RancherOS Documentation
|
||||
description: RancherOS is a simplified Linux distribution built from containers, for containers. These documents describe how to install and use RancherOS.
|
||||
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`. Decause it only includes the services necessary to run Docker, RancherOS is dramatically smaller than most traditional operating systems. 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.
|
||||
|
||||
|
@@ -26,7 +26,7 @@ $ lsmod | grep zfs
|
||||
|
||||
> *Note:* if you switch consoles, you may need to re-run `ros up zfs`.
|
||||
|
||||
#### Using ZFS
|
||||
#### Creating ZFS pools
|
||||
|
||||
After it's installed, it should be ready to use. Make a zpool named `zpool1` using a device that you haven't yet partitioned (you can use `sudo fdisk -l` to list all the disks and their partitions).
|
||||
|
||||
@@ -46,6 +46,14 @@ $ docker run --rm -it -v /mnt/zpool1/:/data alpine ls -la /data
|
||||
|
||||
To experiment with ZFS, you can create zpool backed by just ordinary files, not necessarily real block devices. In fact, you can mix storage devices in your ZFS pools; it's perfectly fine to create a zpool backed by real devices **and** ordinary files.
|
||||
|
||||
#### Using the ZFS debugger utility
|
||||
|
||||
The `zdb` command may be used to display information about ZFS pools useful to diagnose failures and gather statistics. By default the utility tries to load pool configurations from `/etc/zfs/zpool.cache`. Since the RancherOS ZFS service does not make use of the ZFS cache file and instead detects pools by inspecting devices, the `zdb` utility has to be invoked with the `-e` flag.
|
||||
|
||||
E.g. to show the configuration for the pool `zpool_1` you may run the following command:
|
||||
|
||||
> $ sudo zdb -e -C zpool_1
|
||||
|
||||
## ZFS storage for Docker on RancherOS
|
||||
|
||||
First, you need to stop the`docker` system service and wipe out `/var/lib/docker` folder:
|
||||
|
Reference in New Issue
Block a user