Skip to content

Docker Desktop log debugging

Docker Desktop stores operational logs that can be critical for diagnosing startup failures or networking issues within the application. On Windows systems, the primary log file is typically located at /c/Users/<username>/AppData/Local/Docker/log.txt.^[docker-desktop-k8s-startup-fail.md]

One effective method for monitoring the application's behavior in real-time is to stream the log file using the tail command.^[docker-desktop-k8s-startup-fail.md]

tail -f /c/Users/yu_da/AppData/Local/Docker/log.txt

Analyzing Log Errors

The logs contain structured entries that help identify specific failure points. Common errors reported in the backend logs include socket binding issues.^[docker-desktop-k8s-startup-fail.md]

For example, a Kubernetes setup failure might manifest in the logs as a warning (W) related to port exposure:

Error while setting up kubernetes: cannot expose the external port: listen tcp 127.0.0.1:6443: bind: An attempt was made to access a socket in a way forbidden by its access permissions..^[docker-desktop-k8s-startup-fail.md]

This specific error indicates that the Docker backend attempted to bind port 6443 (the default Kubernetes API server port) but was blocked by the system, often due to the Windows NAT (WinNAT) service holding the port.^[docker-desktop-k8s-startup-fail.md]

Troubleshooting Steps

When logs indicate that a socket access was forbidden or a port bind failed, resolving the underlying system conflict is necessary.^[docker-desktop-k8s-startup-fail.md]

If the WinNAT service is causing the conflict, you can stop the service to release the port bindings.^[docker-desktop-k8s-startup-fail.md]

net stop winnat

After stopping the service, you may attempt to restart Docker Desktop to verify that the backend can successfully bind to the required ports.

Sources

  • docker-desktop-k8s-startup-fail.md