New Container: vLLM

[Josephrp]

What is the new container you'd like to have?

A vLLM object container would serve testing and usage better.

Why not just use a generic container for this?

The Ollama object is not maintained against Ollama, which causes several issues:

1. Performance: Ollama performs poorly with batch sizes of 50+ requests.
2. Functionality: The new "search functionality" in Ollama requires ollama keys, which are not supported in the current object.
3. Coverage & Quality: Ollama’s coverage and performance are lower compared to vLLM.

Why vLLM?

The vLLM object allows development and testing in a highly configurable, programmatic way, improving the overall testing experience.

Other references

[alexanderankin]

What relation does this have to the ollama container?

…

On Tue, Sep 30, 2025, 4:58 PM Tonic ***@***.***> wrote: *Josephrp* created an issue (testcontainers/testcontainers-python#885) <#885> *What is the new container you'd like to have?* A *vLLM object container* would serve testing and usage better. *Why not just use a generic container for this?* The *Ollama object* is not maintained against Ollama, which causes several issues: 1. *Performance:* Ollama performs poorly with batch sizes of 50+ requests. 2. *Functionality:* The new "search functionality" in Ollama requires ollama keys, which are not supported in the current object. 3. *Coverage & Quality:* Ollama’s coverage and performance are lower compared to vLLM. *Why vLLM?* The *vLLM object* allows development and testing in a *highly configurable, programmatic way*, improving the overall testing experience. *Other references* — Reply to this email directly, view it on GitHub <#885>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACECGJGQLXDKPNBNK4Z5NRL3VLVFRAVCNFSM6AAAAACH6BMVGOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGQ3TCMBVGE2DIMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Josephrp]

it's a better performing , more configurable , up-to-date "analogue"