From 17a486b80b991615cc95491b5b6d0942f1713731 Mon Sep 17 00:00:00 2001 From: niusmallnan Date: Thu, 2 Aug 2018 17:38:21 +0800 Subject: [PATCH] Remove the description of bootcmd The bootcmd runs during the bootstrap process. In order to boot speed, in fact, now bootstrap does not run every boot. It just runs when you first boot via docker-machine or iPXE. Almost few users can use bootcmd. --- .../configuration/running-commands/_index.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/content/os/v1.x/en/installation/configuration/running-commands/_index.md b/content/os/v1.x/en/installation/configuration/running-commands/_index.md index 5c90d2ecc3e..01bc8047343 100644 --- a/content/os/v1.x/en/installation/configuration/running-commands/_index.md +++ b/content/os/v1.x/en/installation/configuration/running-commands/_index.md @@ -32,16 +32,3 @@ write_files: ``` Running Docker commands in this manner is useful when pieces of the `docker run` command are dynamically generated. For services whose configuration is static, [adding a system service]({{< baseurl >}}/os/v1.x/en/installation/system-services/adding-system-services/) is recommended. - -## Running Commands Early in the Boot Process ---- - -The `bootcmd` parameter can be used to run commands earlier in the boot process. In particular, `bootcmd` will be executed while RancherOS is still running from memory and before System Docker and any system services are started. - -The syntax for bootcmd is the same as `runcmd`. - -```yaml -#cloud-config -bootcmd: -- [ mdadm, --assemble, --scan ] -```