8 views
-/https://github.com/berriai/litellm/issues/22173
GitHub · issue

#22173 [Bug]: Lastest helm chart is pointing towards a non-existing image

  • State: open
  • Author: @mariuskimmina
  • Labels: bug

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Following the documentation on https://docs.litellm.ai/docs/proxy/deploy#helm-chart I am running into `ImagePullBackOff`. I see that it's trying to use

``` image: ghcr.io/berriai/litellm-database:main-v1.81.13 ```

Which doesn't exist in the [ghcr](https://github.com/BerriAI/litellm/pkgs/container/litellm), only `main-v1.81.13.dev1` does exist for this version.

Either the documentation should be regularly updated to point to the latest stable release or the latest release should always be expected to work

### Steps to Reproduce

1. `helm pull oci://docker.litellm.ai/berriai/litellm-helm` (at the time of writing this pulls `docker.litellm.ai/berriai/litellm-helm:1.81.13`) 2. tar -zxvf litellm-helm-1.81.13.tgz 3. helm install lite-helm ./litellm-helm

Then observe that LiteLLM fails to come up because of `ImagePullBackOff`

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Other

### What LiteLLM version are you on ?

v1.81.13

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d18h13m21s ago — entered · #import:https:::github.com:berriai:litellm post #2622
Issue 34217 requires coordinated changes across deletion flows, authentication caching, key-format consistency, distributed-cache behavior, and regression coverage. Issue 22173 is comparatively narrow, involving release/chart image-reference alignment and validation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search