Issue Station
Sign In
Tools hereToolbox

litellm - ✅(Solved) Fix Inaccuracy in the Getting Started Tutorial [2 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26235•Fetched 2026-04-23 07:24:30
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
ildar-shildar-sh
Participants
ayushh0110ayushh0110ildar-shildar-sh
Timeline (top)
cross-referenced ×2labeled ×2commented ×1referenced ×1

Fix Action

Fixed

PR fix notes

PR #26236: docs: remove redundant docker pull step from Docker Compose tutorial

Description (problem / solution / changelog)

Summary

Fixes #26235

The Getting Started Tutorial's Docker Compose tab instructed users to run:

docker pull ghcr.io/berriai/litellm-database:main-latest

However, the downloaded docker-compose.yml doesn't use this image at all — it pulls docker.litellm.ai/berriai/litellm:main-stable and postgres:16, which Docker Compose fetches automatically on first docker compose up. The manual pre-pull step was redundant and confusing.

Changes

  • Remove the "Pull the LiteLLM database image" step from the Docker Compose tab
  • Renumber remaining steps (Step 2 → Step 1, Step 3 → Step 2; subsections 2.x → 1.x)
  • Clarify that the config.yaml volume mount and --config flag are commented out by default in docker-compose.yml (so users know to uncomment them)
  • Fix a duplicate paragraph and a stale section reference (Step 2.4 → Step 1.3) in the Troubleshooting section

Test plan

  • Verify rendered docs look correct in Docusaurus preview
  • Confirm no other references to the removed pull step remain in the file

Changed files

  • docs/my-website/docs/proxy/docker_quick_start.md (modified, +8/-20)

PR #26259: docs: remove misleading Step 1 from Docker Compose quickstart

Description (problem / solution / changelog)

Relevant issues

Fixes #26235

Pre-Submission checklist

  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai

Type

📖 Documentation

Changes

The Getting Started tutorial told users to docker pull ghcr.io/berriai/litellm-database:main-latest as Step 1, but the docker-compose.yml downloaded in the next step uses docker.litellm.ai/berriai/litellm:main-stable and postgres:16 — the litellm-database image is never referenced. This step was a no-op that confused users.

Fix: Remove the redundant step and renumber:

  • Old Step 2 (config files setup) → Step 1
  • Old Step 3 (docker compose up) → Step 2

Changed files

  • docs/my-website/docs/proxy/docker_quick_start.md (modified, +8/-17)
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

On the Getting Started Tutorial, “Step 1 — Pull the LiteLLM database image” instructs docker pull ghcr.io/berriai/litellm-database:main-latest. The same page then has you download docker-compose.yml via curl -O https://raw.githubusercontent.com/BerriAI/litellm/main/docker-compose.yml, and the docker-compose.yml uses: image: docker.litellm.ai/berriai/litellm:main-stable for litellm image: postgres:16 for db So the “pull litellm-database image” step doesn’t match the Compose file you’re instructed to use.

If you use docker-compose, I think step 1 can simply be removed.

Steps to Reproduce

This confusion in the documentation does not lead to errors, but simply misleads the user.

Relevant log output

What part of LiteLLM is this about?

Docs

What LiteLLM version are you on ?

v1.83.11-nightly

Twitter / LinkedIn details

No response

extent analysis

TL;DR

The documentation for the Getting Started Tutorial can be improved by removing the unnecessary "Step 1 — Pull the LiteLLM database image" to avoid confusion.

Guidance

  • Review the docker-compose.yml file to confirm that it uses image: docker.litellm.ai/berriai/litellm:main-stable for litellm and image: postgres:16 for db, which does not match the pulled litellm-database image.
  • Consider removing "Step 1 — Pull the LiteLLM database image" from the tutorial as it does not seem to be necessary when using docker-compose.
  • Verify that the tutorial works as expected after removing the unnecessary step to ensure that it does not introduce any issues.
  • Update the documentation to reflect the correct steps for getting started with LiteLLM using docker-compose.

Notes

The issue is related to the documentation and does not seem to cause any errors, but rather confusion for the user. The suggested fix is to update the documentation to remove the unnecessary step.

Recommendation

Apply workaround: Remove the unnecessary "Step 1 — Pull the LiteLLM database image" from the Getting Started Tutorial to avoid confusion, as the docker-compose.yml file uses a different image.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#LLM response#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING