Skip to content

Commit 6be4baf

Browse files
authored
Merge pull request #100862 from mburke5678/wmco-fix-docker-420
[enterprise-4.20] OSDOCS WMCO remove docker references
2 parents 07ff6c8 + 6805840 commit 6be4baf

File tree

4 files changed

+26
-33
lines changed

4 files changed

+26
-33
lines changed
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * support/troubleshooting/troubleshooting-windows-container-workload-issues.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="collecting-docker-logs-windows_{context}"]
7+
= Collecting containerd logs for Windows containers
8+
9+
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.
10+
11+
.Prerequisites
12+
13+
* You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
14+
* You have created a Windows compute machine set.
15+
16+
.Procedure
17+
18+
* View the containerd logs by running the following command:
19+
+
20+
[source,terminal]
21+
----
22+
$ oc adm node-logs -l kubernetes.io/os=windows --path=containerd
23+
----

modules/collecting-docker-logs-windows.adoc

Lines changed: 0 additions & 29 deletions
This file was deleted.

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,9 @@ $ oc adm node-logs -l kubernetes.io/os=windows --path=journal
2323
+
2424
The same command is executed when collecting logs with `oc adm must-gather`.
2525
+
26-
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:
26+
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:
2727
+
2828
[source,terminal]
2929
----
30-
$ oc adm node-logs -l kubernetes.io/os=windows --path=journal -u docker
30+
$ oc adm node-logs -l kubernetes.io/os=windows --path=journal -u containerd
3131
----

support/troubleshooting/troubleshooting-windows-container-workload-issues.adoc

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,12 +22,11 @@ include::modules/accessing-windows-node-using-rdp.adoc[leveloffset=+2]
2222

2323
include::modules/collecting-kube-node-logs-windows.adoc[leveloffset=+1]
2424
include::modules/collecting-windows-application-event-logs.adoc[leveloffset=+1]
25-
include::modules/collecting-docker-logs-windows.adoc[leveloffset=+1]
25+
include::modules/collecting-containerd-logs-windows.adoc[leveloffset=+1]
2626

2727
[role="_additional-resources"]
2828
== Additional resources
2929

3030
* link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/troubleshooting[Containers on Windows troubleshooting]
3131
* 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]
32-
* link:https://docs.docker.com/docker-for-windows/troubleshoot/[Docker for Windows troubleshooting]
3332
* link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/common-problems[Common Kubernetes problems with Windows]

0 commit comments

Comments
 (0)