Docker Desktop Issues
Troubleshoot common Docker Desktop issues that may prevent Xyte Edge from running on Windows.
Troubleshoot common Docker Desktop issues that may prevent Xyte Edge from running on Windows.
Prerequisite — Docker Desktop must be running before any Edge troubleshooting can begin.If Docker Desktop is closed, crashed, or not fully started, the Edge container cannot run and none of the troubleshooting commands will work. Always confirm Docker Desktop is open and the engine is running (green dot in the taskbar) before proceeding.
Quick checklist
Before running any command, confirm all three:
| # | Check | How to verify |
|---|---|---|
| 1 | Docker Desktop is open | Whale icon visible in the Windows taskbar (bottom-right) |
| 2 | Docker Engine is running | Docker Desktop shows a green Engine running status |
| 3 | Edge container is visible | Run docker ps in Command Prompt — xyte_edge should appear |
If any check fails, find your scenario in the table below.
Troubleshoot common Docker Desktop issues using the table below.
Scenario or error | Likely meaning | Recommended next steps |
|---|---|---|
Docker Desktop: Not open or missing from taskbar | Docker Desktop was not launched after Windows started, or was closed. | Open Docker Desktop from the Start Menu and wait up to 2 minutes for the engine to initialize. Look for the whale icon in the taskbar and confirm it shows Engine running. |
Docker Desktop: Stuck on loading after opening | Docker Engine is still initializing or got stuck on startup. | Wait a full 2 minutes. If still stuck, right-click the taskbar icon and select Restart Docker Desktop. If that fails, reboot Windows and reopen Docker Desktop. |
Docker Desktop: Stopped working after power loss or reboot | Docker Desktop was interrupted and did not cleanly restart. | Fully reboot your Windows machine. Open Docker Desktop before anything else and wait for the green Engine running status before running any commands. |
Docker Desktop: Permission denied while trying to connect to Docker API | Your Windows user does not have permission to access the Docker daemon. | To fix it permanently: |
Docker Desktop: You have reached your pull rate limit | Docker Hub is rate-limiting image pulls for your account or IP. | Next steps: |
Docker Desktop: docker ps returns an error or shows nothing | Docker Engine is not running or the Edge container has not started. | Confirm Docker Desktop shows Engine running. |
Docker Desktop: Telnet or connectivity test is not working | The telnet command must be run inside the Edge container, not from a Windows CMD window. |
|
Docker Desktop: How to collect Docker Desktop diagnostic logs | You need Docker Desktop logs to share with the support team. | Open Docker Desktop, click the gear icon, go to Troubleshoot, click Get support, and select Download diagnostics. Share the file with the Xyte support team. |
Docker Desktop: How to extract Edge container logs | You need Xyte Edge container logs for review or support. | Use the command that matches your operating system: Linux/macOS docker logs -t xyte_edge > xyte_edge_logs.txt 2>&1Windows CMD docker logs -t xyte_edge > xyte_edge_logs.txt 2>&1Windows PowerShell docker logs -t xyte_edge 2>&1 | Out-File -FilePath xyte_edge_logs.txt |
Not sure where to start?
| # | Question | If No — action |
|---|---|---|
| 1 | Is Docker Desktop open? | Open it from the Start Menu and wait for the engine to start |
| 2 | Is Docker Engine running (green dot)? | Restart Docker Desktop. If it won't start, reboot Windows. |
| 3 | Does docker ps show xyte_edge? | Restart the Xyte Edge application, then run docker ps again |
Only after all three are confirmed should you continue to Edge-specific troubleshooting steps.
If Docker Desktop is running, xyte_edge appears in docker ps, and the issue still continues, collect Docker Desktop diagnostics and Edge container logs before contacting Xyte support.
Additional resources
Last updated: 2026-05-03
Updated about 2 hours ago
