Skip to content
Snippets Groups Projects
Unverified Commit c3605018 authored by 杨刚  (成都)'s avatar 杨刚 (成都) Committed by GitHub
Browse files

fix typo in doc. (#9728)


Signed-off-by: default avataryanggang <gang.yang@daocloud.io>
parent 8523f525
No related branches found
No related tags found
No related merge requests found
...@@ -45,7 +45,7 @@ Note: When Ansible is already installed via system packages on the control node, ...@@ -45,7 +45,7 @@ Note: When Ansible is already installed via system packages on the control node,
Python packages installed via `sudo pip install -r requirements.txt` will go to Python packages installed via `sudo pip install -r requirements.txt` will go to
a different directory tree (e.g. `/usr/local/lib/python2.7/dist-packages` on a different directory tree (e.g. `/usr/local/lib/python2.7/dist-packages` on
Ubuntu) from Ansible's (e.g. `/usr/lib/python2.7/dist-packages/ansible` still on Ubuntu) from Ansible's (e.g. `/usr/lib/python2.7/dist-packages/ansible` still on
buntu). As a consequence, the `ansible-playbook` command will fail with: Ubuntu). As a consequence, the `ansible-playbook` command will fail with:
```raw ```raw
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path. ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
......
...@@ -66,7 +66,7 @@ apt-get install pigz ...@@ -66,7 +66,7 @@ apt-get install pigz
### 5) Run `cluster.yml` playbook with `--limit` ### 5) Run `cluster.yml` playbook with `--limit`
```commandline ```commandline
ansible-playbook cluster.yml -i inventory/sample/hosts.ini cluster.yml --limit=NODENAME ansible-playbook -i inventory/sample/hosts.ini cluster.yml --limit=NODENAME
``` ```
This effectively reinstalls containerd and seems to place all config files in the right place. When this completes, kubelet will immediately pick up the new container engine and start spinning up DaemonSets and kube-system Pods. This effectively reinstalls containerd and seems to place all config files in the right place. When this completes, kubelet will immediately pick up the new container engine and start spinning up DaemonSets and kube-system Pods.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment