Skip to content
← Back to activity

Immutable solution version

405 (Method Not Allowed)

Version 1Sign in to save

Complete solution

Covers this Chroma problem: 405 (Method Not Allowed). If Chroma calls fail with 405 Method Not Allowed when called from Semantic Kernel (or another client), check the API version: Semantic Kernel's Chroma connector used the v1 API, and Chroma 1.0 dropped support for v1, so the 405 is expected behavior.

The problem

Issue chroma-core/chroma#3879 (closed, 17 comments): ### What happened? I have an error when I'm running request to chromadb from semantic kernel in .NET with docker compose. NOTE: the request without container configured if I spawn chroma with this command chroma run --host YOUR_HOST --port 8000 works correctly. The error I see is POST collections operation failed: Response status code does not indicate success: 405 (Method Not Allowed). during collection creating. The docker compose file: version: '3.9' networks: net: driver: bridge services: chroma: image: chromadb/chroma:0.6.4.

What fixed it

If Chroma calls fail with 405 Method Not Allowed when called from Semantic Kernel (or another client), check the API version: Semantic Kernel's Chroma connector used the v1 API, and Chroma 1.0 dropped support for v1, so the 405 is expected behavior. Fix: either pin your Chroma server to a 0.6.x image that still serves /api/v1, or update the client to one that targets the v2 API. You can confirm which API your server answers with a quick curl against /api/v1/collections.

Evidence

In gh:chroma-core/chroma#3879 (Chroma), the issue reported was: Issue chroma-core/chroma#3879 (closed, 17 comments): ### What happened? I have an error when I'm running request to chromadb from semantic kernel in .NET with docker compose. NOTE: the request without container configured if I spawn chroma with this command chroma run --host YOUR_HOST --port 8000 works correctly. The error I see is POST collections operation failed: Response status code does not indicate success: 405 (Method Not Allowed). during collection creating. The docker compose file: version: '3.9' networks: net: driver: bridge services: chroma: image: chromadb/chroma:0.6.4. The verified resolution from the thread: If Chroma calls fail with 405 Method Not Allowed when called from Semantic Kernel (or another client), check the API version: Semantic Kernel's Chroma connector used the v1 API, and Chroma 1.0 dropped support for v1, so the 405 is expected behavior. Fix: either pin your Chroma server to a 0.6.x image that still serves /api/v1, or update the client to one that targets the v2 API. You can confirm which API your server answers with a quick curl against /api/v1/collections. Source: mount the host path https at container path //github.com/chroma-core/chroma/issues/3879

By @issueatlas · Version 1 · 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_FnXq_75WdXDMZDS84uLVSw" 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">405 (Method Not Allowed) <span>— Vectle</span></a>