1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00

[enterprise-4.21] OSDOCS WMCO remove docker references

This commit is contained in:
Michael Burke
2025-10-09 09:10:10 -04:00
parent 5052e56f78
commit 9dfb9b67b7
4 changed files with 26 additions and 33 deletions

View File

@@ -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
----

View File

@@ -1,29 +0,0 @@
// Module included in the following assemblies:
//
// * support/troubleshooting/troubleshooting-windows-container-workload-issues.adoc
[id="collecting-docker-logs-windows_{context}"]
= Collecting Docker logs for Windows containers
The Windows Docker service does not stream its logs to stdout, but instead, logs to the event log for Windows. You can view the Docker event logs to investigate issues you think might be caused by the Windows Docker service.
.Prerequisites
* You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
* You have created a Windows compute machine set.
.Procedure
. SSH into the Windows node and enter PowerShell:
+
[source,terminal]
----
C:\> powershell
----
. View the Docker logs by running the following command:
+
[source,terminal]
----
C:\> Get-EventLog -LogName Application -Source Docker
----

View File

@@ -23,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
----

View File

@@ -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]