Troubleshooting

Use these checks when Echo does not open as expected or cannot show your local Docker resources.

Docker is unavailable

If Echo opens but cannot show containers or other resources, confirm that your Docker-compatible engine is installed and running.

You can also run a quick terminal check:

docker ps

If that command cannot connect, start Docker Desktop, Colima, Lima, OrbStack, or your preferred local engine, then reopen Echo.

The current MVP build is unsigned. macOS or Windows may block the app on first launch.

Use the first-run steps in Getting Started and make sure you downloaded Echo from the official GitHub Releases page.

If the app does not launch after extraction, try extracting the archive again with your system archive tool.

On Linux, confirm the extracted binary has execute permission:

chmod +x echo

If logs or shell sessions do not open, confirm that the target container is still running and that Docker is responsive.

Restarting the affected container can help if the container exited or became unhealthy during local development.