Troubleshooting
Common issues and how to resolve them — connection problems, permissions, performance, and Kubernetes.
Common issues and the quickest way to resolve each one.
Can't connect to Docker daemon
Use the tabs below to match the platform you are on.
Make sure Docker Desktop is running, then check Settings → Docker settings for the socket path Dockerman should use.
Choose between Docker Desktop and the WSL2 Engine in Windows. If Dockerman is pointed at the wrong backend, switch it in Settings → Docker settings.
Add your user to the docker group and follow Linux permissions.
Permission errors on Linux
If Dockerman cannot reach /var/run/docker.sock, add your user to the docker group, log out and back in, and verify that docker ps works without sudo.
WSL2 Setup Wizard fails
Use the Windows troubleshooting section for the WSL2 path: Windows platform troubleshooting.
SSH host connection fails
Check the host port, private key file permissions, and any firewall rule that blocks outbound port 22. For the full setup flow, see Remote Hosts.
Performance issues
- High CPU when idle usually means a Logs tab is streaming a large file set. Pause tabs you are not using.
- Slow list loads with hundreds of containers usually means you need to filter by status or Compose project first.
- Sluggish stats usually means the selected time range is too wide. Reduce it to 1h or 3h.
Kubernetes: k3d fails to start
Kubernetes: kubeconfig import fails
- Pick the correct context name when you import the kubeconfig.
- Refresh expired credentials, then export the kubeconfig again.
- Verify that
kubectl get nsworks from the command line before you import behind a proxy or firewall.
Collecting logs
Open the App Log page first. If you need to file an issue, export the App Log and attach it with the Dockerman version.
Getting help
File issues on the Dockerman GitHub repository and attach the App Log export plus the Dockerman version from Settings → About.