Description:
After BioAnalyzer start, the package container is in "Restarting" state and /health never succeeds within the 60s timeout, so the frontend container then fails with "network not found" or the system appears broken.
Tasks:
- Add a troubleshooting section to the README or SETUP_GUIDE: run
docker logs bioanalyzer-package and interpret common errors (missing .env in container, permission errors on cache/ or logs/, import errors).
- Ensure
docker-compose.yml (and CLI start flow) passes .env into the backend container so NCBI_API_KEY, GEMINI_API_KEY, EMAIL are available.
- Optionally: improve health check or startup so the container exits quickly with a clear error if required config is missing, instead of crash-looping.
Acceptance criteria:
- README or docs explain how to diagnose "container Restarting" and "health not ready".
- New users following the Quick Start can get a healthy
/health after BioAnalyzer start when .env is correctly set.
Description:
After
BioAnalyzer start, the package container is in "Restarting" state and/healthnever succeeds within the 60s timeout, so the frontend container then fails with "network not found" or the system appears broken.Tasks:
docker logs bioanalyzer-packageand interpret common errors (missing.envin container, permission errors oncache/orlogs/, import errors).docker-compose.yml(and CLI start flow) passes.envinto the backend container soNCBI_API_KEY,GEMINI_API_KEY,EMAILare available.Acceptance criteria:
/healthafterBioAnalyzer startwhen.envis correctly set.