Skip to content
← Back to activity

Immutable solution version

ChromaDB 0.4+ is no longer compatible with client config

Version 2Sign in to save

Complete solution

Shows how to fix chromaDB 0.4+ is no longer compatible with client config. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Upgrading langchain from 0.0.228 to 0.0.325 fixed it. Another reporter's case was caused by a stale chromadbimpl='duckdb+parquet' in their.env; removing it fixed that.

Steps

  1. - [ ] LLMs/Chat Models
  • [ ] Embedding Models
  • [ ] Prompts / Prompt Templates / Prompt Selectors
  • [ ] Output Parsers
  • [ ] Document Loaders
  • [X] Vector Stores / Retrievers
  • [ ] Memory
  • [ ] Agents / Agent Executors
  • [ ] Tools / Toolkits
  • [ ] Chains
  • [ ] Callbacks/Tracing
  • [ ] Async
  1. [mrinterestfull (reporter)]: The deprecated configuration of Chroma error came from old langchain, not chroma. Upgrading langchain from 0.0.228 to 0.0.325 fixed it. Another reporter's case was caused by a stale chromadbimpl='duckdb+parquet' in their .env; removing it fixed that.

When to use

You are seeing this: Issue langchain-ai/langchain#7887 (closed, 51 comments): ### System Info - Python 3.9.13 - langchain-0.0.235-py3-none-any.whl - chromadb-0.4.0-py3-none-any.whl Use this skill when you run into "ChromaDB 0.4+ is no longer compatible with client config".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: Python 3.9.13, langchain- 0.0.235-py3, chromadb- 0.4.0-py3, 0.0.228, 0.0.325. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

In gh:langchain-ai/langchain#7887 (LangChain), the issue reported was: Issue langchain-ai/langchain#7887 (closed, 51 comments): ### System Info

  • Python 3.9.13
  • langchain-0.0.235-py3-none-any.whl
  • chromadb-0.4.0-py3-none-any.whl

Who can help?

No response

Information

  • [ ] The official example notebooks/scripts
  • [x] My own modified scripts

Related Components

  • [ ] LLMs/Chat Models
  • [ ] Embedding Models
  • [ ] Prompts / Prompt Templates / Prompt Selectors
  • [ ] Output Parsers
  • [ ] Document Loaders
  • [X] Vector Stores / Retrievers
  • [ ] Memory
  • [ ] Agents / Agent Executors
  • [ ] Tools / Toolkits
  • [ ] Chains
  • [ ] Callbacks/Tracing
  • [ ] Async

Reproduction

Steps to reproduce:

1.... The verified resolution from the thread: [mrinterestfull (reporter)]: The deprecated configuration of Chroma error came from old langchain, not chroma. Upgrading langchain from 0.0.228 to 0.0.325 fixed it. Another reporter's case was caused by a stale chromadbimpl='duckdb+parquet' in their .env; removing it fixed that. Source: mount the host path https at container path //github.com/langchain-ai/langchain/issues/7887

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_yk_jTPc_5mjpaKMIixfiFQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ChromaDB 0.4+ is no longer compatible with client config <span>— Vectle</span></a>