We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
A small change to get alot of reliability back....
We see vLLM crash or hang in various ways, e.g.:
#4108 #4344
And manually managing that is a hassle.
vLLM team could easily add a HEALTHCHECK line in the Dockerfile so tools like autoheal can function.
https://hub.docker.com/r/willfarrell/autoheal/ https://docs.docker.com/reference/dockerfile/#healthcheck
Would looks like:
HEALTHCHECK --interval=5m --timeout=10s curl -f http://localhost/health || exit 1
This would allow one to use the other docker image to manage the vLLM images.
Manual labor
No response
The text was updated successfully, but these errors were encountered:
@pseudotensor
Can you open a PR?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
馃殌 The feature, motivation and pitch
A small change to get alot of reliability back....
We see vLLM crash or hang in various ways, e.g.:
#4108
#4344
And manually managing that is a hassle.
vLLM team could easily add a HEALTHCHECK line in the Dockerfile so tools like autoheal can function.
https://hub.docker.com/r/willfarrell/autoheal/
https://docs.docker.com/reference/dockerfile/#healthcheck
Would looks like:
This would allow one to use the other docker image to manage the vLLM images.
Alternatives
Manual labor
Additional context
No response
The text was updated successfully, but these errors were encountered: