Troubleshooting
For local-setup specific issues, check the local-setup issues on GitHub.
Common Issues
Docker/Podman Not Running
- Ensure Docker Desktop or Podman is started
- For WSL2: Verify Docker Desktop WSL integration is enabled
Port Conflicts
- Ensure ports 8443, 80, and 443 are not in use by other applications
- Stop conflicting services before running setup
Cluster Creation Fails
If the Kind cluster fails to create:
# Delete the existing cluster
kind delete cluster --name platform-mesh
# Retry setup
task local-setupCheck available disk space (need ~10GB) and verify your container runtime has sufficient resources.
Certificate Trust Issues
Quick Fix:
# Reinstall certificates
mkcert -installIf you continue to see certificate warnings in your browser, you may need platform-specific setup. See the certificate troubleshooting guide for detailed instructions for WSL2, Windows, Linux, and Firefox users.
Component Timeout Issues
- Try to use the cached version, as it needs less image pulling and try again using
task local-setup:cached - Verify all required images can be pulled
Debug Mode
For more verbose output, prepend DEBUG=true to any task:
DEBUG=true task local-setup:iterateWSL2 Specific Issues
If Kubernetes is crashing because of a conflict between Cgroup v1 and v2 (a "hybrid" state), you can force WSL2 to use Cgroup v2 exclusively (Unified Mode). This is the modern standard starting from Kubernetes v1.25, where Cgroup v2 graduated to General Availability (GA).
- Open PowerShell on Windows.
- Edit your
.wslconfigfile:notepad $env:USERPROFILE\.wslconfig - Add these lines:
[wsl2]
# Disable Cgroup V1 to force the kernel into "unified" (v2 only) mode
kernelCommandLine = cgroup_no_v1=allComponent Timeout Issues
- Try to use the cached version, as it needs less image pulling and try again using
task local-setup-cached - Verify all required images can be pulled
Cleaning Up
To remove the local setup:
# Delete the Kind cluster
kind delete cluster --name platform-mesh
# Remove certificates (optional)
mkcert -uninstall