kevinthedang / discord-ollama

Discord Bot that utilizes Ollama to interact with any Large Language Models to talk with users and allow them to host/create their own models.
Creative Commons Attribution 4.0 International
73 stars 8 forks source link

Ollama Docker Container Startup Errors #38

Closed kevinthedang closed 5 months ago

kevinthedang commented 5 months ago

Steps to Reproduce

Error

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: nvml error: driver/library version mismatch: unknown
Error: failed to start containers: ollama

This might be a result of the new ollama docker container release a 2 days ago. Will be investigating.

Need to run for debugging:

kevinthedang commented 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.

image

JT2M0L3Y commented 5 months ago

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!

image

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.

JT2M0L3Y commented 5 months ago

@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. image

kevinthedang commented 5 months ago

Seems like this is somehow still an issue, reopening this issue.

image

kevinthedang commented 5 months ago

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.

kevinthedang commented 5 months ago

Alright I suppose there is no issue right now. Might just be a server issue!