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:

#CheckHow to verify
1Docker Desktop is openWhale icon visible in the Windows taskbar (bottom-right)
2Docker Engine is runningDocker Desktop shows a green Engine running status
3Edge container is visibleRun 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:
1. Right-click the Docker Desktop icon and select Run as administrator.
2. Wait for the engine to start, then try again.
3. If the error persists, contact your IT administrator.

Docker Desktop: You have reached your pull rate limit

Docker Hub is rate-limiting image pulls for your account or IP.

Next steps:
1. Review Docker's pull rate guidance: Increase rate limits.
2. Check your current pull usage: View pull rate and limit.
3. Sign in to Docker Desktop with your Docker account.
4. Upgrade your plan if you hit this limit often.

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.
1. Run docker ps in Command Prompt.
2. If xyte_edge is not listed, restart the Xyte Edge application.
3. Run docker ps again.

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.

  1. Run docker ps and confirm xyte_edge is listed.
    2. Run docker exec -it xyte_edge bash to enter the container.
    3. Run the telnet command from inside the container.

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>&1

Windows CMD
docker logs -t xyte_edge > xyte_edge_logs.txt 2>&1

Windows PowerShell
docker logs -t xyte_edge 2>&1 | Out-File -FilePath xyte_edge_logs.txt

Not sure where to start?

#QuestionIf No — action
1Is Docker Desktop open?Open it from the Start Menu and wait for the engine to start
2Is Docker Engine running (green dot)?Restart Docker Desktop. If it won't start, reboot Windows.
3Does 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