RunpodR
Runpod•3mo ago•
7 replies
zz_zac

Container fails to start

I'm getting the following logs when running:
Using the custom container: verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2

c2ab5d43600d Pull complete
Digest: sha256:8ec276d967e6cbfa307eed9206ebb7d5197c770c1436e6153a2f9e6fc7b487c8
Status: Downloaded newer image for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2
create container verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2
app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2 Pulling from verlai/verl
Digest: sha256:8ec276d967e6cbfa307eed9206ebb7d5197c770c1436e6153a2f9e6fc7b487c8
Status: Image is up to date for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2
start container for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2: begin
start container for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2: begin
start container for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2: begin
start container for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2: begin
start container for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2: begin
start container for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2: begin
start container for verlai/verl:app-verl0.5-transformers4.55.4-vllm0.10.0-mcore0.13.0-te2.2: begin
Was this page helpful?