[GH-ISSUE #2680] Server misbehaving pulling models #27356

Closed
opened 2026-04-22 04:39:08 -05:00 by GiteaMirror · 7 comments
Owner

Originally created by @bradstallion on GitHub (Feb 22, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2680

Hi,
I've just updated the ollama docker image.
Trying pulling gemma:

$ ollama pull gemma:7b
pulling manifest 
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/gemma/manifests/7b": dial tcp: lookup registry.ollama.ai on 131.114.21.25:53: server misbehaving

Same problem with other models (such as Mixtral)

Originally created by @bradstallion on GitHub (Feb 22, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2680 Hi, I've just updated the ollama docker image. Trying pulling gemma: ``` $ ollama pull gemma:7b pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/gemma/manifests/7b": dial tcp: lookup registry.ollama.ai on 131.114.21.25:53: server misbehaving ``` Same problem with other models (such as Mixtral)
Author
Owner

@jaifar530 commented on GitHub (Feb 22, 2024):

install cloudflare VPN and try again https://1.1.1.1

<!-- gh-comment-id:1959745067 --> @jaifar530 commented on GitHub (Feb 22, 2024): install cloudflare VPN and try again https://1.1.1.1
Author
Owner

@bradstallion commented on GitHub (Feb 22, 2024):

Thanks but I don't get it. Why should I install a VPN to access Ollama models?

<!-- gh-comment-id:1959749523 --> @bradstallion commented on GitHub (Feb 22, 2024): Thanks but I don't get it. Why should I install a VPN to access Ollama models?
Author
Owner

@mxyng commented on GitHub (Feb 22, 2024):

Cloudflare VPN is not necessary to use Ollama.

dial tcp: lookup registry.ollama.ai on 131.114.21.25:53: server misbehaving

This suggests there's an issue with DNS (port 53). Can you confirm the container has access to the outside world and resolves well known hosts such as google.com?

<!-- gh-comment-id:1960060663 --> @mxyng commented on GitHub (Feb 22, 2024): Cloudflare VPN is not necessary to use Ollama. > dial tcp: lookup registry.ollama.ai on 131.114.21.25:53: server misbehaving This suggests there's an issue with DNS (port 53). Can you confirm the container has access to the outside world and resolves well known hosts such as google.com?
Author
Owner

@bradstallion commented on GitHub (Feb 22, 2024):

Good point. The answer is no. I run the container this way:

docker run -d --gpus=all -v /tmp:/DATA -v `pwd`/volume:/root/.ollama -p 11434:11434 --name ollama ollama/ollama

And it used to work, until this morning.
Adding the --network=host option:

docker run -d --network=host --gpus=all -v /tmp:/DATA -v `pwd`/volume:/root/.ollama --name ollama ollama/ollama

works.

Strange, but good for me.
Thanks

<!-- gh-comment-id:1960114349 --> @bradstallion commented on GitHub (Feb 22, 2024): Good point. The answer is no. I run the container this way: ``` docker run -d --gpus=all -v /tmp:/DATA -v `pwd`/volume:/root/.ollama -p 11434:11434 --name ollama ollama/ollama ``` And it used to work, until this morning. Adding the --network=host option: ``` docker run -d --network=host --gpus=all -v /tmp:/DATA -v `pwd`/volume:/root/.ollama --name ollama ollama/ollama ``` works. Strange, but good for me. Thanks
Author
Owner

@xiaoyi001yeye commented on GitHub (Apr 20, 2024):

$ollama pull llama3:8b
pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/llama3/manifests/8b": dial tcp: lookup registry.ollama.ai on 127.0.0.11:53: server misbehaving

我使用的本地的ollama命令,没有使用docker

完结:我把ollama的docker容器停了,本地的ollama命令就能正常的更新了

<!-- gh-comment-id:2067649961 --> @xiaoyi001yeye commented on GitHub (Apr 20, 2024): $ollama pull llama3:8b pulling manifest Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/llama3/manifests/8b": dial tcp: lookup registry.ollama.ai on 127.0.0.11:53: server misbehaving 我使用的本地的ollama命令,没有使用docker 完结:我把ollama的docker容器停了,本地的ollama命令就能正常的更新了
Author
Owner

@JBGruber commented on GitHub (May 3, 2024):

I ran into this issue just now. Exposing just port 53 also worked for me.

<!-- gh-comment-id:2092920805 --> @JBGruber commented on GitHub (May 3, 2024): I ran into this issue just now. Exposing just port 53 also worked for me.
Author
Owner

@queeup commented on GitHub (Nov 18, 2025):

I solve this problem with put dns address of my router: --dns 192.168.1.1

<!-- gh-comment-id:3549478853 --> @queeup commented on GitHub (Nov 18, 2025): I solve this problem with put dns address of my router: `--dns 192.168.1.1`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#27356