You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes - we would like to use --entrypoint=/bin/bash to enable using image with non-default entrypoint as RunPod base image, like the official vLLM image vllm/vllm-openai:latest. That image comes with an entrypoint ["python3", "-m", "vllm.entrypoints.openai.api_server"] (reference here).
Describe the solution you'd like
Adding another argument docker_run_args in the create_pod API. That will be
Describe alternatives you've considered
Maybe just adds a boolean flag to override the entrypoint with /bin/bash - I guess it is common to use an image with proper dependency but a non-default entrypoint.
Additional context
Using vllm/vllm-openai:latest as base image gave me this error:
Is your feature request related to a problem? Please describe.
Yes - we would like to use
--entrypoint=/bin/bash
to enable using image with non-default entrypoint as RunPod base image, like the official vLLM imagevllm/vllm-openai:latest
. That image comes with an entrypoint["python3", "-m", "vllm.entrypoints.openai.api_server"]
(reference here).Describe the solution you'd like
Adding another argument
docker_run_args
in thecreate_pod
API. That will beDescribe alternatives you've considered
Maybe just adds a boolean flag to override the entrypoint with
/bin/bash
- I guess it is common to use an image with proper dependency but a non-default entrypoint.Additional context
Using
vllm/vllm-openai:latest
as base image gave me this error:The script I use to create the pod is similar to #337, but only change the
image_name
arguments.The text was updated successfully, but these errors were encountered: