Spaces:
Running
Running
fix: increase healthcheck start-period to 180s
Browse filesGateway ready timeout is 120s but healthcheck start-period was 90s.
With heavier image (Chromium + JupyterLab), container took longer
than 90s to become ready causing premature 503 → HF restart loop.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Dockerfile +1 -1
Dockerfile
CHANGED
|
@@ -97,7 +97,7 @@ ENV HERMES_HOME=/opt/data \
|
|
| 97 |
|
| 98 |
EXPOSE 7861
|
| 99 |
|
| 100 |
-
HEALTHCHECK --interval=30s --timeout=5s --start-period=
|
| 101 |
CMD curl -fsS http://localhost:7861/health || exit 1
|
| 102 |
|
| 103 |
CMD ["/opt/huggingmes/start.sh"]
|
|
|
|
| 97 |
|
| 98 |
EXPOSE 7861
|
| 99 |
|
| 100 |
+
HEALTHCHECK --interval=30s --timeout=5s --start-period=180s \
|
| 101 |
CMD curl -fsS http://localhost:7861/health || exit 1
|
| 102 |
|
| 103 |
CMD ["/opt/huggingmes/start.sh"]
|