Closed kevinthedang closed 5 months ago
Possible temporary solution? @JT2M0L3Y
Simply just revert to an older version of the container and see? Otherwise we are cooked with this new container and should make an issue on the official GitHub.
Looking at the Ollama GitHub I was able to pull version 0.1.31. After making sure this was the only ollama container available, I was able to spin up both containers successfully!
That is to say, I "rolled forward" one version instead of rolling back. I will check next if the 0.1.30 version is working yet.
@kevinthedang I believe this issue has been fixed. I am going to assume the fix was to run the commands initally listed from the server to restart the docker service.
Both versions (0.1.31 and 0.1.30) now work successfully with the npm run start
command.
Seems like this is somehow still an issue, reopening this issue.
Seems like this is an issue with the Nvidia Drivers or the version of the Nvidia Container Toolkit. Seems like the current solution is to restart the server. Likely to investigate later.
Alright I suppose there is no issue right now. Might just be a server issue!
Steps to Reproduce
docs/
npm run start
Error
This might be a result of the new ollama docker container release a 2 days ago. Will be investigating.
Need to run for debugging:
systemctl stop docker
dockerd --debug
docker start ollama