Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
Kubespray
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Model registry
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Mirror
Kubespray
Commits
c3605018
Unverified
Commit
c3605018
authored
2 years ago
by
杨刚 (成都)
Committed by
GitHub
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
fix typo in doc. (#9728)
Signed-off-by:
yanggang
<
gang.yang@daocloud.io
>
parent
8523f525
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
README.md
+1
-1
1 addition, 1 deletion
README.md
docs/upgrades/migrate_docker2containerd.md
+1
-1
1 addition, 1 deletion
docs/upgrades/migrate_docker2containerd.md
with
2 additions
and
2 deletions
README.md
+
1
−
1
View file @
c3605018
...
...
@@ -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
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
buntu). As a consequence, the
`ansible-playbook`
command will fail with:
U
buntu). As a consequence, the
`ansible-playbook`
command will fail with:
```
raw
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
...
...
This diff is collapsed.
Click to expand it.
docs/upgrades/migrate_docker2containerd.md
+
1
−
1
View file @
c3605018
...
...
@@ -66,7 +66,7 @@ apt-get install pigz
### 5) Run `cluster.yml` playbook with `--limit`
```
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 diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment