github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 00:51:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #2697] Unable to build Ollama on Cluster #1610

New Issue
Closed
opened 2026-04-12 11:32:24 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-12 11:32:24 -05:00
Owner
Copy Link

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

Originally assigned to: @dhiltgen on GitHub.

Hi,
Thanks for this great work. I am trying to build Ollama on my cluster and I don't have administrative access. My cluster has the following configuration:

LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	CentOS
Description:	CentOS Linux release 7.9.2009 (Core)
Release:	7.9.2009
Codename:	Core

I follow these steps:

a) Clone the ollama repo using: git clone https://github.com/ollama/ollama

b) Following https://github.com/ollama/ollama/blob/main/docs/development.md, I do go generate ./... but I get the error:

image

I tried cloning the repo with the recursive submodules but it didn't help me much. Also, I tried older commits but it wasn't helpful either.

Originally created by @Anirudh257 on GitHub (Feb 22, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2697 Originally assigned to: @dhiltgen on GitHub. Hi, Thanks for this great work. I am trying to build Ollama on my cluster and I don't have administrative access. My cluster has the following configuration: ``` LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.9.2009 (Core) Release: 7.9.2009 Codename: Core ``` I follow these steps: a) Clone the ollama repo using: `git clone https://github.com/ollama/ollama` b) Following https://github.com/ollama/ollama/blob/main/docs/development.md, I do `go generate ./...` but I get the error: ![image](https://github.com/ollama/ollama/assets/16001446/5651b8bf-8722-47f3-bff3-0753bcdfb9f2) I tried cloning the repo with the recursive submodules but it didn't help me much. Also, I tried older commits but it wasn't helpful either.
GiteaMirror commented 2026-04-12 11:32:25 -05:00
Author
Owner
Copy Link

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

How is the repo cloned? It can be a problem if the ollama repo is itself a submodule which looks to be the case here.

You can skip this with by setting OLLAMA_SKIP_PATCHING to a non-empty value but this may leave the repo in a undefined state so it should be used as a last resort.

<!-- gh-comment-id:1960617220 --> @mxyng commented on GitHub (Feb 23, 2024): How is the repo cloned? It can be a problem if the ollama repo is itself a submodule which looks to be the case here. You can skip this with by setting `OLLAMA_SKIP_PATCHING` to a non-empty value but this may leave the repo in a undefined state so it should be used as a last resort.
GiteaMirror commented 2026-04-12 11:32:26 -05:00
Author
Owner
Copy Link

@Anirudh257 commented on GitHub (Feb 23, 2024):

Hi @mxyng I cloned it normally using the command: git clone https://github.com/ollama/ollama I also tried with the --recursive flag to clone all the submodules but it didn't help either.

<!-- gh-comment-id:1960785426 --> @Anirudh257 commented on GitHub (Feb 23, 2024): Hi @mxyng I cloned it normally using the command: `git clone https://github.com/ollama/ollama` I also tried with the `--recursive` flag to clone all the submodules but it didn't help either.
GiteaMirror commented 2026-04-12 11:32:26 -05:00
Author
Owner
Copy Link

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

What version of git are you using?

<!-- gh-comment-id:1961906265 --> @mxyng commented on GitHub (Feb 23, 2024): What version of git are you using?
GiteaMirror commented 2026-04-12 11:32:27 -05:00
Author
Owner
Copy Link

@Anirudh257 commented on GitHub (Feb 23, 2024):

Hi, @mxyng I am using the ollama version 0.1.6. However, I found a workaround utilizing the compiled binary provided in https://github.com/ollama/ollama/blob/main/docs/linux.md#download-the-ollama-binary It works fine although the build issue persists.

<!-- gh-comment-id:1962006025 --> @Anirudh257 commented on GitHub (Feb 23, 2024): Hi, @mxyng I am using the ollama version `0.1.6`. However, I found a workaround utilizing the compiled binary provided in https://github.com/ollama/ollama/blob/main/docs/linux.md#download-the-ollama-binary It works fine although the build issue persists.
GiteaMirror commented 2026-04-12 11:32:27 -05:00
Author
Owner
Copy Link

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

Can you describe your build environment, specifically distro and its version, so we can try to reproduce?

I'm curious. Is there a specific reason you're interested in 0.1.6? There's been significant improvements since 0.1.6 so I'd suggest update as soon as possible.

<!-- gh-comment-id:1962037711 --> @mxyng commented on GitHub (Feb 23, 2024): Can you describe your build environment, specifically distro and its version, so we can try to reproduce? I'm curious. Is there a specific reason you're interested in 0.1.6? There's been significant improvements since 0.1.6 so I'd suggest update as soon as possible.
GiteaMirror commented 2026-04-12 11:32:28 -05:00
Author
Owner
Copy Link

@Anirudh257 commented on GitHub (Feb 23, 2024):

Hi, there is no specific reason for me to use 0.1.6.

Sure, my build environment is a slurm cluster having this config:

image

My GPU is:

image

I am using the commit version:

git show

image

<!-- gh-comment-id:1962094148 --> @Anirudh257 commented on GitHub (Feb 23, 2024): Hi, there is no specific reason for me to use 0.1.6. Sure, my build environment is a slurm cluster having this config: ![image](https://github.com/ollama/ollama/assets/16001446/b7116e2e-18a3-4a3b-87ce-3d2ded277e54) My GPU is: ![image](https://github.com/ollama/ollama/assets/16001446/1adb8e06-1550-4deb-b9c7-172409d7b1e8) I am using the commit version: `git show` ![image](https://github.com/ollama/ollama/assets/16001446/d1e24d49-f051-4e4d-ac6b-3b13d5720d38)
GiteaMirror commented 2026-04-12 11:32:28 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Mar 12, 2024):

I'm fairly sure this is due to an old git version in your cluster. I don't know what the minimum version is that's required to be able to init a submodule from a child directory in the repo, but if you can upgrade git, I believe the problem should go away.

<!-- gh-comment-id:1989670173 --> @dhiltgen commented on GitHub (Mar 12, 2024): I'm fairly sure this is due to an old `git` version in your cluster. I don't know what the minimum version is that's required to be able to init a submodule from a child directory in the repo, but if you can upgrade git, I believe the problem should go away.
GiteaMirror commented 2026-04-12 11:32:29 -05:00
Author
Owner
Copy Link

@Anirudh257 commented on GitHub (Mar 12, 2024):

Hi @dhiltgen Sure, I will retry. Thanks!

<!-- gh-comment-id:1991833488 --> @Anirudh257 commented on GitHub (Mar 12, 2024): Hi @dhiltgen Sure, I will retry. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#1610
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?