public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 21:18:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into audit-17

Browse Source
This commit is contained in:
Robert Parker
2019-10-08 11:16:37 -07:00
committed by GitHub
parent deb369dc30 01b3cb13ca
commit 96af9b675b
113 changed files with 3889 additions and 1433 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/os/v1.x/en/installation/configuration/date-and-timezone/_index.md
+22
View File
@@ -0,0 +1,22 @@
---
title: Date and time zone
weight: 121
---
The default console keeps time in the Coordinated Universal Time (UTC) zone and synchronizes clocks with the Network Time Protocol (NTP). The Network Time Protocol daemon (ntpd) is an operating system program that maintains the system time in synchronization with time servers using the NTP.
RancherOS can run ntpd in the System Docker container. You can update its configurations by updating `/etc/ntp.conf`. For an example of how to update a file such as `/etc/ntp.conf` within a container, refer to [this page.]({{< baseurl >}}/os/v1.x/en/installation/configuration/write-files/#writing-files-in-specific-system-services)
The default console cannot support changing the time zone because including `tzdata` (time zone data) will increase the ISO size. However, you can change the time zone in the container by passing a flag to specify the time zone when you run the container:
```
$ docker run -e TZ=Europe/Amsterdam debian:jessie date
Tue Aug 20 09:28:19 CEST 2019
```
You may need to install the `tzdata` in some images:
```
$ docker run -e TZ=Asia/Shanghai -e DEBIAN_FRONTEND=noninteractive -it --rm ubuntu /bin/bash -c "apt-get update && apt-get install -yq tzdata && date”
Thu Aug 29 08:13:02 CST 2019
```
content/os/v1.x/en/installation/configuration/docker/_index.md
+3 -3
View File
@@ -86,7 +86,7 @@ _Available as of v1.4.x_
The docker0 bridge can be configured with docker args, it will take effect after reboot.
```
$ ros config set rancher.docker.bip 192.168.100.1/16
$ ros config set rancher.docker.bip 192.168.0.0/16
```
### Configuring System Docker
@@ -114,13 +114,13 @@ _Available as of v1.4.x_
The docker-sys bridge can be configured with system-docker args, it will take effect after reboot.
```
$ ros config set rancher.system_docker.bip 172.18.43.1/16
$ ros config set rancher.system_docker.bip 172.19.0.0/16
```
_Available as of v1.4.x_
The default path of system-docker logs is `/var/log/system-docker.log`. If you want to write the system-docker logs to a separate partition,
e.g. [RANCHE_OEM partition]({{< baseurl >}}/os/v1.x/en/about/custom-partition-layout/#use-rancher-oem-partition), you can try `rancher.defaults.system_docker_logs`:
e.g. [RANCHER_OEM partition]({{< baseurl >}}/os/v1.x/en/about/custom-partition-layout/#use-rancher-oem-partition), you can try `rancher.defaults.system_docker_logs`:
```
#cloud-config
content/os/v1.x/en/installation/running-rancheros/cloud/vmware-esxi/_index.md
+1 -1
View File
@@ -7,7 +7,7 @@ As of v1.1.0, RancherOS automatically detects that it is running on VMware ESXi,
As of v1.5.0, RancherOS releases anything required for VMware, which includes initrd, a standard ISO for VMware, a `vmdk` image, and a specific ISO to be used with Docker Machine. The open-vm-tools is built in to RancherOS, there is no need to download it.
| Description | Downlaod URL |
| Description | Download URL |
|---|---|
| Booting from ISO | https://releases.rancher.com/os/latest/vmware/rancheros.iso |
| For docker-machine | https://releases.rancher.com/os/latest/vmware/rancheros-autoformat.iso |
content/os/v1.x/en/installation/system-services/custom-system-services/_index.md
+6 -6
View File
@@ -165,12 +165,12 @@ Once you have your own Services repository, you can add a new service to its ind
To create your own console images, you need to:
1 install some basic tools, including an ssh daemon, sudo, and kernel module tools
2 create `rancher` and `docker` users and groups with UID and GID's of `1100` and `1101` respectively
3 add both users to the `docker` and `sudo` groups
4 add both groups into the `/etc/sudoers` file to allow password-less sudo
5 configure sshd to accept logins from users in the `docker` group, and deny `root`.
6 set `ENTRYPOINT ["/usr/bin/ros", "entrypoint"]`
1. install some basic tools, including an ssh daemon, sudo, and kernel module tools
2. create `rancher` and `docker` users and groups with UID and GID's of `1100` and `1101` respectively
3. add both users to the `docker` and `sudo` groups
4. add both groups into the `/etc/sudoers` file to allow password-less sudo
5. configure sshd to accept logins from users in the `docker` group, and deny `root`.
6. set `ENTRYPOINT ["/usr/bin/ros", "entrypoint"]`
the `ros` binary, and other host specific configuration files will be bind mounted into the running console container when its launched.