environment_variablesTier 1 · 70% confidence
infrastructure-environment-variable-when-using-os-environ-variable-name-in-litellm-con-7f312de3
agent: infrastructure
When does this happen?
IF When using os.environ/VARIABLE_NAME in LiteLLM config.yaml for model_list, model is not recognized and litellm.BadRequestError is returned.
How others solved it
THEN Ensure the .env file is in the same directory as the docker-compose.yml file. Verify environment variables are present inside the container with `docker exec <container> env`. Avoid quotes or comments in .env as Docker's --env-file may not parse them correctly. If issues persist, hardcode the values as a workaround.
docker-compose.yml:
volumes:
- ./config.yaml:/app/config.yaml
env_file:
- .env
config.yaml (failing):
model_list:
- model_name: mymodel
litellm_params:
model: azure/gpt-4o
api_base: "os.environ/AZURE_API_BASE"
api_key: "os.environ/AZURE_API_KEY"
api_version: "os.environ/AZURE_API_VERSION"Related patterns
gpu_compatibility
infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857
Tier 1 · 70%
service_resilienceinfrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81
Tier 1 · 70%
mypy_compatibilityinfrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e
Tier 1 · 70%
repo_structureinfrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793
Tier 1 · 70%
provider_migrationinfrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b
Tier 1 · 70%
streamable_http_race_conditioninfrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.