custom client seems working not as expected with apple silicon mac
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.5k
- Forks
- 1.2k
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
I am trying ollama.Client to connect a remote server for chat.
server A: http://192.168.0.123:11434, ollama installed with docker, ollama-python v0.2.0
local machine: m1 max macbook pro, ollama installed with docker, ollama-python v0.2.0
when using default ollama.chat, i can connect in both environment;
then i tried to connect to server from local machine using
ollama.Client(host='http://192.168.0.123:11434')
and i received 503 error with '' message when commiting code
_client.chat(model="svjack/qwen1_5_14b:latest",
messages=[
{"role": "user", "content": prompt},
],
).
At first, i thought it might has something todo with nerwork, so i did some test.
i tried same script directly on server A, and it runs ok.
then i tried ollama webui on local machine, and i changed default url to server A, and it runs ok.(local machine and server A has a different model list, and it changes properly with config change, it proves.)
then it occurs to me that maybe it has something with mac develop envs.
and i tried the same script on the 3rd machine, it also runs ok.
right now i cant say for sure that the issues has something to do with apple silicon, but it is the best guess i can make.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported script with ollama.Client(host='http://192.168.0.123:11434') and compare it with the working default ollama.chat call. Check whether the client request differs when connecting to the remote Docker server, then verify the result against the working server-side and third-machine tests; done means the cause of the 503 is identified and the remote client call works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100