This guide provides solutions to common issues you might encounter while working with this project.
Problem: docker compose commands fail with errors like Network ... Resource is still in use or containers fail to start with Module not found errors even when the files exist.
Solution: This can happen if the Docker environment is in a bad state. Here are a few steps to resolve this:
- Ensure Docker Desktop is running: The Docker engine must be running for any
dockerordocker composecommands to work. On Windows and macOS, this is typically managed by the Docker Desktop application. - Restart Docker Desktop: If you encounter persistent issues with networks or containers, restarting Docker Desktop can often resolve them.
- Reboot your machine: In some cases, a full reboot of your machine may be necessary to reset the Docker environment completely.
- Rebuild the images: If you are still having issues, especially after adding new files, a full rebuild of the images can help. Use the command
docker compose up --build --no-cache -d.
Problem: ImportError: No module named 'crewai'
Solution: Ensure you're using the latest version:
pip install --upgrade crewai[tools]>=0.177.0Problem: The frontend fails to start with Module not found errors, even after creating missing files.
Solution: This can be caused by a stale Docker volume. Try rebuilding the frontend image from scratch:
docker compose up --build --no-cache -d frontendProblem: WebSocket connection failed
Solution: Check that the backend is running on port 8000:
curl http://localhost:8000/Problem: Agent execution timeout or Search failed
Solution: Check API key configuration:
# Verify .env file contains valid keys
cat .env | grep OPENAI_API_KEY
cat .env | grep SERPER_API_KEYProblem: SerperDevTool authentication failed
Solution: Get a FREE Serper API key:
- Visit https://serper.dev/
- Sign up for a free account (100 searches/month)
- Copy your API key
- Add to your .env file:
SERPER_API_KEY=your-key-here