kooapk 12 Posted March 2, 2023 Posted March 2, 2023 After restarting the Windows computer, emby cannot start. Error reporting is related to the drive of hardware acceleration. Hardware acceleration has been enabled root@future:~/kooapk/kooapk-kitchen# docker start emby Error response from daemon: 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: mount error: stat failed: /usr/lib/wsl/lib/libcuda.so.1.0.0: no such file or directory: unknown Error: failed to start containers: emby root@future:~/kooapk/kooapk-kitchen# ls -l /usr/lib/wsl/lib/libcuda.so.1.0.0 ls: cannot access '/usr/lib/wsl/lib/libcuda.so.1.0.0': No such file or directory root@future:~/kooapk/kooapk-kitchen# ldconfig root@future:~/kooapk/kooapk-kitchen# ls -l /usr/lib/wsl/lib/libcuda.so.1.0.0 ls: cannot access '/usr/lib/wsl/lib/libcuda.so.1.0.0': No such file or directory root@future:~/kooapk/kooapk-kitchen# ls -l /usr/lib/wsl/lib/libcuda.so.1 lrwxrwxrwx 1 root root 14 Mar 2 17:41 /usr/lib/wsl/lib/libcuda.so.1 -> libcuda.so.1.1 root@future:~/kooapk/kooapk-kitchen# ls -l /usr/lib/wsl/lib/libcuda.so.1 lrwxrwxrwx 1 root root 14 Mar 2 17:41 /usr/lib/wsl/lib/libcuda.so.1 -> libcuda.so.1.1 root@future:~/kooapk/kooapk-kitchen# The file/usr/lib/wsl/lib/libcuda. so. 1.0.0 originally exists and a soft link is created to point to/usr/lib/wsl/lib/libcuda. so. 1 It seems that Windows has upgraded a certain driver
Solution kooapk 12 Posted March 2, 2023 Author Solution Posted March 2, 2023 apt update && apt upgrade have already been solved 1 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now