Merge pull request #100278 from mburke5678/wmco-fix-docker

OSDOCS WMCO remove docker references

Author: mburke5678

modules/collecting-containerd-logs-windows.adoc

@@ -0,0 +1,23 @@
+// Module included in the following assemblies:
+//
+// * support/troubleshooting/troubleshooting-windows-container-workload-issues.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="collecting-docker-logs-windows_{context}"]
+= Collecting containerd logs for Windows containers
+
+The Windows containerd container service does not stream log data to stdout, but instead, it stream log data to the Windows event log. You can view the containerd event logs to investigate issues you think might be caused by the Windows containerd container service.
+
+.Prerequisites
+
+* You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
+* You have created a Windows compute machine set.
+
+.Procedure
+
+* View the containerd logs by running the following command:
++
+[source,terminal]
+----
+$ oc adm node-logs -l kubernetes.io/os=windows --path=containerd
+----

modules/collecting-docker-logs-windows.adoc

@@ -2,7 +2,6 @@
 //
 // * support/troubleshooting/troubleshooting-windows-container-workload-issues.adoc
 
-:_mod-docs-content-type: PROCEDURE
 [id="collecting-windows-application-event-logs_{context}"]
 = Collecting Windows application event logs
 
@@ -24,9 +23,9 @@ $ oc adm node-logs -l kubernetes.io/os=windows --path=journal
 +
 The same command is executed when collecting logs with `oc adm must-gather`.
 +
-Other Windows application logs from the event log can also be collected by specifying the respective service with a `-u` flag. For example, you can run the following command to collect logs for the docker runtime service:
+Other Windows application logs from the event log can also be collected by specifying the respective service with a `-u` flag. For example, you can run the following command to collect logs for the containerd container runtime service:
 +
 [source,terminal]
 ----
-$ oc adm node-logs -l kubernetes.io/os=windows --path=journal -u docker
+$ oc adm node-logs -l kubernetes.io/os=windows --path=journal -u containerd
 ----

modules/collecting-windows-application-event-logs.adoc

@@ -22,12 +22,11 @@ include::modules/accessing-windows-node-using-rdp.adoc[leveloffset=+2]
 
 include::modules/collecting-kube-node-logs-windows.adoc[leveloffset=+1]
 include::modules/collecting-windows-application-event-logs.adoc[leveloffset=+1]
-include::modules/collecting-docker-logs-windows.adoc[leveloffset=+1]
+include::modules/collecting-containerd-logs-windows.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 == Additional resources
 
 * link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/troubleshooting[Containers on Windows troubleshooting]
 * link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/update-containers#troubleshoot-host-and-container-image-mismatches[Troubleshoot host and container image mismatches]
-* link:https://docs.docker.com/docker-for-windows/troubleshoot/[Docker for Windows troubleshooting]
 * link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/common-problems[Common Kubernetes problems with Windows]