Closed jerin-scalers-ai closed 1 month ago
hi @jerin-scalers-ai , please setting --privileged=true
when starting the container.
Thanks. It worked by setting --privileged=true
. I haven't faced this issue on a slightly older version of vllm (0.5.3.post1). The VLLM_CPU_OMP_THREADS_BIND was working out of box without --privileged=true
. It will be great if you can include this instruction in the documentation.
Your current environment
vLLM version: v0.6.0 (CPU) CPU: AMD EPYC 9654
π Describe the bug
vLLM v0.6.0 (CPU) server failed to start on setting VLLM_CPU_OMP_THREADS_BIND as shown below:
vLLM Error Log:
Before submitting a new issue...