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

Merge pull request #969 from niusmallnan/custom-system-docker-logs-path

Browse Source 
Custom the file path of system-docker logs
This commit is contained in:
Denise
2018-11-07 21:12:04 -08:00
committed by GitHub
parent ac1acf272e 03490244d3
commit 7cabb301da
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/os/v1.x/en/installation/configuration/docker/_index.md
+13 -1
View File
@@ -93,7 +93,7 @@ Key | Value | Default | Description
`extra_args` | List of Strings | `[]` | Arbitrary daemon arguments, appended to the generated command `extra_args` | List of Strings | `[]` | Arbitrary daemon arguments, appended to the generated command
`environment` | List of Strings (optional) | `[]` | `environment` | List of Strings (optional) | `[]` |
_Available as of v1.4_ _Available as of v1.4.x_
The docker-sys bridge can be configured with system-docker args, it will take effect after reboot. The docker-sys bridge can be configured with system-docker args, it will take effect after reboot.
@@ -101,6 +101,18 @@ The docker-sys bridge can be configured with system-docker args, it will take ef
$ ros config set rancher.system_docker.bip 172.18.43.1/16 $ ros config set rancher.system_docker.bip 172.18.43.1/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`:
```
#cloud-config
rancher:
defaults:
system_docker_logs: /usr/share/ros/oem/system-docker.log
```
### Using a pull through registry mirror ### Using a pull through registry mirror
There are 3 Docker engines that can be configured to use the pull-through Docker Hub registry mirror cache: There are 3 Docker engines that can be configured to use the pull-through Docker Hub registry mirror cache: