ollama - 💡(How to fix) Fix Qwen3.5 MLX models fail to run — config.json not found in manifest [10 comments, 7 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
ollama/ollama#15171Fetched 2026-04-08 01:58:25
View on GitHub
Comments
10
Participants
7
Timeline
28
Reactions
8
Timeline (top)
subscribed ×12commented ×10mentioned ×3closed ×1

Error Message

500 Internal Server Error: mlx runner failed: Error: failed to read config.json: config "config.json" not found in manifest (exit: exit status 1)

Code Example

500 Internal Server Error: mlx runner failed: Error: failed to read config.json: config "config.json" not found in manifest (exit: exit status 1)

---

ollama pull qwen3.5:35b-a3b-mlx-bf16 && ollama pull qwen3.5:9b-mlx-bf16 && ollama pull qwen3.5:27b-mlx-bf16
pulling manifest
pulling model: 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  70 GB
writing manifest
success
Could not detect context length for qwen3.5:35b-a3b-mlx-bf16, skipping
pulling manifest
pulling model: 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  18 GB
writing manifest
success
Could not detect context length for qwen3.5:9b-mlx-bf16, skipping
pulling manifest
pulling model: 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  54 GB
writing manifest
success
Could not detect context length for qwen3.5:27b-mlx-bf16, skipping
RAW_BUFFERClick to expand / collapse

What is the issue?

All three Qwen3.5 MLX tags from the registry pull successfully but are completely non-functional at runtime. Affected tags:

  • qwen3.5:35b-a3b-mlx-bf16
  • qwen3.5:9b-mlx-bf16
  • qwen3.5:27b-mlx-bf16

Attempting to run (e.g. CLI, OpenWebUI, Ollama GUI) results in error:

500 Internal Server Error: mlx runner failed: Error: failed to read config.json: config "config.json" not found in manifest (exit: exit status 1)

Relevant log output

ollama pull qwen3.5:35b-a3b-mlx-bf16 && ollama pull qwen3.5:9b-mlx-bf16 && ollama pull qwen3.5:27b-mlx-bf16
pulling manifest
pulling model: 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  70 GB
writing manifest
success
⚠ Could not detect context length for qwen3.5:35b-a3b-mlx-bf16, skipping
pulling manifest
pulling model: 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  18 GB
writing manifest
success
⚠ Could not detect context length for qwen3.5:9b-mlx-bf16, skipping
pulling manifest
pulling model: 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  54 GB
writing manifest
success
⚠ Could not detect context length for qwen3.5:27b-mlx-bf16, skipping

OS

macOS

GPU

Apple

CPU

Apple

Ollama version

ollama version is 0.19.0

extent analysis

TL;DR

The issue can likely be resolved by ensuring the config.json file is properly included in the manifest for the Qwen3.5 MLX tags.

Guidance

  • Verify that the config.json file exists and is correctly referenced in the manifest for each of the affected tags (qwen3.5:35b-a3b-mlx-bf16, qwen3.5:9b-mlx-bf16, qwen3.5:27b-mlx-bf16).
  • Check the manifest files for any discrepancies or errors that might prevent the config.json file from being found.
  • Consider re-pulling the tags or re-writing the manifests to ensure consistency and accuracy.
  • Investigate the warnings about unable to detect context length for each tag, as this might be related to the issue or indicate a separate problem.

Example

No specific code snippet can be provided without more context on the manifest files or how they are generated.

Notes

The issue seems to be related to the configuration or packaging of the MLX tags rather than the Ollama version or the hardware (GPU, CPU, OS). The warnings about context length detection might be worth exploring further.

Recommendation

Apply a workaround by manually verifying and correcting the manifest files for the affected tags to ensure the config.json file is properly included and referenced. This approach is chosen because it directly addresses the error message provided and allows for a targeted fix without requiring an upgrade or assuming additional issues.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING