Merge pull request #63735 from neolit123/kubeadm-init-stdout-update

Automatic merge from submit-queue (batch tested with PRs 63735, 62807). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

kubeadm-init: update note about failing containers

**What this PR does / why we need it**:

This PR was merged before all requested changes
were applied:
kubernetes/pull/59731

Update the note about failing containers as requested here:
https://github.com/kubernetes/kubernetes/pull/59731#pullrequestreview-119517427

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
NONE

**Special notes for your reviewer**:
NONE

**Release note**:

```release-note
NONE
```

cmd/kubeadm/app/cmd/init.go

@@ -104,13 +104,12 @@ var (
 			- 'systemctl status kubelet'
 			- 'journalctl -xeu kubelet'
 
-		Additionally a control plane component may not have come up in docker. If that's the case, you can enumerate 
+		Additionally, a control plane component may have crashed or exited when started by the container runtime.
-		all docker containers that have been started (including ones that have crashed and exited) by running the
+		To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
-		following commands:
+		Here is one example how you may list all Kubernetes containers running in docker:
-			- 'docker ps -a'
+			- 'docker ps -a | grep kube | grep -v pause'
-		
+			Once you have found the failing container, you can inspect its logs with:
-		Once you have that list, you can inspect the logs for any pod with:
+			- 'docker logs CONTAINERID'
-			- 'docker logs $CONTAINERID'
 		`)))
 )