Open thalesfsp opened 3 months ago
dusty-nv
commented
3 months ago Hi @thalesfsp, there isn't a github action that gets triggered by external repos. However you can build it anytime with jetson-containers build ollama
But first I recommend following some of these setup steps, in particular adding an NVME or additional storage and relocating your docker root to it: https://github.com/dusty-nv/jetson-containers/blob/master/docs/setup.md
thalesfsp
commented
2 months ago Hello @dusty-nv! If no GA builds the images, how/who builds the images, for example, the Ollama one?
dusty-nv
commented
2 months ago @thalesfsp I build/push the images from here, it is just difficult to debug/fix them and keep up with the changes, so anyone is welcome to make PRs (which is how these initially came about) or point to ollama commits with the patches.
mtebenev
commented
2 months ago @dusty-nv While not directly related, in the docker file the version is exported as: export VERSION=$(git describe --tags --first-parent --abbrev=7 --long --dirty --always | sed -e "s/^v//g") && \ (i.e. short hash). It does not work well with some models. For example ollama run llama3.1 fails with message stating that the newer version is required. According to the ollama docs "export VERSION="0.0.0" - will work well (and works for me actually). Shall I prepare a PR or there some reason to not use "0.0.0"?
dusty-nv
commented
2 months ago @mtebenev that is good to know about version 0.0.0, I will keep that in mind should this issue recur again in the future - it was previously requested to have valid ollama versions in the container (at which time I added that export VERSION=$(git describe --tags --first-parent --abbrev=7 --long --dirty --always | sed -e "s/^v//g") command to the Dockerfile lifted from the ollama codebase)
Maybe removing the --long --dirty flags from the git describe invocation will remove the .g1234819 part that is giving it trouble. Otherwise, yea I err on the side of going back to 0.0.0 to prevent it in the future. For now, I am just rebuilding for ollama 3.9 which should avoid the llama 3.1 issue (will push to dustynv/ollama:r36.3.0)
rayrrr
commented
2 months ago
Hello, how can I update Ollama to the latest version? Or, how can build the Ollama image so every time they update the version, I can just trigger the build by my self? Is there some GitHub action automatically building when upstream changes? Best regards!