[BUG] TGI versions inconsistency / use of old TGI versions

[eero-t]

Currently latest used TGI versions in this repo are v2.3.1 (Gaudi) / v2.4.1 (CPU).

However there are several files where much older versions are used.

GenAIExamples, old CPU/rocm versions:

GenAIExamples$ git grep text-generation-inference: | grep -v -e github -e 2.[34].[01]
AudioQnA/kubernetes/gmc/README.md:- tgi-service: ghcr.io/huggingface/text-generation-inference:1.4
ChatQnA/docker_compose/nvidia/gpu/compose.yaml:    image: ghcr.io/huggingface/text-generation-inference:2.2.0
DBQnA/docker_compose/intel/cpu/xeon/README.md:docker run -d --name="test-text2sql-tgi-endpoint" --ipc=host -p $TGI_PORT:80 -v ./data:/data --shm-size 1g -e HUGGINGFACEHUB_API_TOKEN=${HUGGINGFACEHUB_API_TOKEN} -e HF_TOKEN=${HF_TOKEN} -e model=${model} ghcr.io/huggingface/text-generation-inference:2.1.0 --model-id $model
DBQnA/docker_compose/intel/cpu/xeon/compose.yaml:    image: ghcr.io/huggingface/text-generation-inference:2.1.0
DocSum/tests/test_compose_on_rocm.sh:    docker pull ghcr.io/huggingface/text-generation-inference:1.4
DocSum/tests/test_compose_on_xeon.sh:    docker pull ghcr.io/huggingface/text-generation-inference:1.4
FaqGen/tests/test_compose_on_xeon.sh:    docker pull ghcr.io/huggingface/text-generation-inference:1.4
MultimodalQnA/docker_compose/amd/gpu/rocm/compose.yaml:    image: ghcr.io/huggingface/text-generation-inference:3.0.1-rocm

GenAIComps, old CPU versions:

GenAIComps$ git grep text-generation-inference: | grep -v -e github -e 2.[34].[01]
comps/text2sql/src/README.md:docker run -d --name="text2sql-tgi-endpoint" --ipc=host -p $TGI_PORT:80 -v ./data:/data --shm-size 1g -e HF_TOKEN=${HUGGINGFACEHUB_API_TOKEN} -e model=${LLM_MODEL_ID} ghcr.io/huggingface/text-generation-inference:2.1.0 --model-id $LLM_MODEL_ID

GenAIExamples, old Gaudi versions (latest used version is 2.3.1):

$ git grep tgi-gaudi:2.0 | wc -l
40

PS. All TEI image references are for 1.5 version, i.e. consistent.

[xiguiw]

@eero-t
Thanks! Good catch.

Do you have plan to submit PR to fix this?

[eero-t]

Do you have plan to submit PR to fix this?

@xiguiw No.

(Fixing this could be a good "beginner" / "first time" task PR.)

[zhanmyz]

OPEA_Team4 is working on this issue