Make ollama container tag/version configurable

[feO2x]

Related to an existing integration?

Yes

Existing integration

CommunityToolkit.Aspire.Hosting.Ollama

Overview

Version 9.4.1-beta.280 of CommunityToolkit.Aspire.Hosting.Ollama does not allow to set the specific version of Ollama that should be run inside a container. It's hardcoded to Ollama 0.6.0 - the newest version is 0.6.8. This results in newer models like mistral-small31:32b not being executable with CommunityToolkit.Aspire.Hosting.Ollama because it requires a newer Ollama version than 0.6.0.

Usage example

We could add a method overload that takes an additional tag parameter:

distributedApplicationBuilder.AddOllama("ollama", tag: "0.6.8");

Or an additional method on the IResourceBuilder<OllamaResource>:

distributedApplicationBuilder
    .AddOllama("ollama")
    .WithImageTag("0.6.8");

Breaking change?

No

Alternatives

As the tag value is a constant value in OllamaContainerImageTags, I don't see any alternatives.

Additional context

This could also come in handy when implementing #608. Imagine if there was another parameter where we specify that Ollama shouldn't be run in a container but simply accessed via a dedicated HTTP/HTTPS URL, the CommunityToolkit.Aspire.Hosting.Ollama could know this way which version is used (although we could also call ollama version).

Help us help you

Yes, I'd like to be assigned to work on this item

[Alirexaa]

You can use WithImageTag to override the tag.