Ollama Not Working in Docker

So i was trying to use the latest ollama but does not work at all i replaced the env file with 1134 link and also the docker format of host . internal etc as well but no luck can anyone put a guide for this to run ollama properly

Hey @aarishcs2! Sorry you are running into this. Could you copy your system setup from the debug tab in the settings? You can find by clicking on the tab in the top left, then going to the settings in the bottom left and enabling the debug feature.

so i did that and i keep getting this error even when i run without docker

Cannot read properties of undefined (reading ‘toolCalls’)
at Object.flush (file:///D:/bolt.diy/node_modules/ai/core/generate-text/stream-text.ts:569:33)
at invokePromiseCallback (node:internal/webstreams/util:162:10)
at Object. (node:internal/webstreams/util:167:23)
at transformStreamDefaultSinkCloseAlgorithm (node:internal/webstreams/transformstream:621:43)
at node:internal/webstreams/transformstream:379:11
at writableStreamDefaultControllerProcessClose (node:internal/webstreams/writablestream:1162:28)
at writableStreamDefaultControllerAdvanceQueueIfNeeded (node:internal/webstreams/writablestream:1242:5)
at writableStreamDefaultControllerClose (node:internal/webstreams/writablestream:1209:3)
at writableStreamClose (node:internal/webstreams/writablestream:722:3)
at writableStreamDefaultWriterClose (node:internal/webstreams/writablestream:1091:10)
at writableStreamDefaultWriterCloseWithErrorPropagation (node:internal/webstreams/writablestream:1083:10)
at node:internal/webstreams/readablestream:1558:15
at complete (node:internal/webstreams/readablestream:1437:9)
at processTicksAndRejections (node:internal/process/task_queues:105:5

no idea how to fix this

i believe bolt is not able to load ollama model list from server side and using default model

we should add some logs in before the LLM calls

1 Like

what is your setup for ollama is it on docker too?
and what is your version hash of bolt you are using ?

1 Like

I believe the toolCalls error happens if you install using npm install instead of using pnpm install, and it could be for just one or many models. Can also be causes by vite having an issue or missing.

Try deleting the node_modules folder and run npm install pnpm & pnpm install & pnpm run dev.