Document Details
Troubleshoot
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
cmd_examples
⚠️
missing_linux_example
Summary:
The documentation provides a mix of Bash and CMD examples, but in several sections, Windows CMD syntax is used without equivalent Linux/Bash examples, especially for commands like 'iotedge logs', 'docker rm', and 'iotedge restart'. Some code blocks are marked as 'cmd' or use Windows-centric syntax, and in a few cases, the documentation does not clarify cross-platform differences or provide Linux alternatives. While the initial troubleshooting steps use Bash, later sections implicitly assume Windows usage or present Windows commands first.
Recommendations:
- For every CMD/Windows example, provide an equivalent Bash/Linux example side-by-side or clearly indicate cross-platform compatibility.
- Use neutral code block labeling (e.g., 'shell') unless the command is truly platform-specific.
- Clarify any differences in command usage or output between Windows and Linux environments.
- Audit all command examples to ensure Linux users are not left to infer the correct syntax or behavior.
- Where tools or paths differ between platforms, explicitly document both.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-22 00:01 | #88 | completed | ✅ Clean |
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
* On the Azure portal, use the built-in troubleshoot tool. For more information, see [Troubleshoot IoT Edge devices from the Azure portal](troubleshoot-in-portal.md).
* Use the [UploadModuleLogs direct method](how-to-retrieve-iot-edge-logs.md#upload-module-logs) to upload the logs of a module to Azure Blob Storage.
## Clean up container logs
By default the Moby container engine doesn't set container log size limits. Over time extensive logs can lead to the device filling up with logs and running out of disk space. If large container logs are affecting your IoT Edge device performance, use the following command to force-remove the container along with its related logs.
If you're still troubleshooting, wait until after you inspect the container logs to take this step.
>[!WARNING]
>If you force remove the edgeHub container while it has an undelivered message backlog and no [host storage](how-to-access-host-storage-from-module.md) configured, the undelivered messages are lost.