Replies: 5 comments
-
Reads like you started a CPU AIO, but the container still pulled Nvidia dependencies and became sad when there was no CUDA hardware to talk to. This happened to me to, but good @mudler is working on a fix |
Beta Was this translation helpful? Give feedback.
-
same here. |
Beta Was this translation helpful? Give feedback.
-
Can't replicate this:
Are you having nvidia-container runtime installed ? looks like a host misconfiguration |
Beta Was this translation helpful? Give feedback.
-
Nvidia SMI is indeed installed on this host, and there are two graphics cards. But I didn't want to use a graphics card, so I downloaded the CPU version. It's okay, I have found other alternative products, haha, thank you! |
Beta Was this translation helpful? Give feedback.
-
Ha nice, i’m all new to this. What are you using now? |
Beta Was this translation helpful? Give feedback.
-
[root@localhost ~]# docker run -ti --name local-ai -p 28098:8080 localai/localai:latest-aio-cpu
docker: 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 #1: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: invalid expression: unknown.
ERRO[0000] error waiting for container:
[root@localhost ~]#
Beta Was this translation helpful? Give feedback.
All reactions