Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Docker won't start anymore because of the Nvidia GPU #239

Closed
1 task done
Crylia opened this issue Mar 17, 2024 · 9 comments
Closed
1 task done

[BUG] Docker won't start anymore because of the Nvidia GPU #239

Crylia opened this issue Mar 17, 2024 · 9 comments

Comments

@Crylia
Copy link

Crylia commented Mar 17, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Docker worked fine with my 1660 for a while but now it suddenly won't start anymore

Expected Behavior

Docker to function normal

Steps To Reproduce

Install docker
Install nvidia driver
confirm both working
add --gpu-all in the docker params
see it not working anymore

Environment

- OS: Unraid 6.12.8
- How docker service was installed: Via unraid

CPU architecture

x86-64

Docker creation

docker run
  -d
  --name='jellyfin'
  --net='bridge'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Bocchi"
  -e HOST_CONTAINERNAME="jellyfin"
  -e 'JELLYFIN_PublishedServerUrl'='192.168.0.26'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8096]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/jellyfin-logo.png'
  -p '8096:8096/tcp'
  -p '8920:8920/tcp'
  -p '7359:7359/udp'
  -p '1900:1900/udp'
  -v '/mnt/user/Jellyfin/':'/data/tvshows':'rw'
  -v '/mnt/user/Jellyfin/':'/data/movies':'rw'
  -v '/mnt/user/Jellyfin/':'/media':'rw'
  -v '/mnt/user/jellyfin_data/':'/config':'rw'
  --gpus all 'lscr.io/linuxserver/jellyfin:latest'

15bb8699383217bc43a142677de7a0cabb4245a7db5bac531731083e485918ff
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 #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: open failed: /proc/sys/kernel/overflowuid: permission denied: unknown.

The command failed.

Container logs

None, won't start
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@Roxedus
Copy link
Member

Roxedus commented Mar 17, 2024

This looks very much with a issue for the nvidia toolkit, and probably not a container issue.

@j0nnymoe
Copy link
Member

Last I checked, --gpus all isn't the way you do this. You need to set the nvidia runtime + the ENV's required.

@Crylia
Copy link
Author

Crylia commented Mar 18, 2024

Last I checked, --gpus all isn't the way you do this. You need to set the nvidia runtime + the ENV's required.

This is how I had it originally, I removed it because it wouldn't work and since the exact same issue came up with --gpus all I figured it would be sufficient

@Crylia
Copy link
Author

Crylia commented Mar 18, 2024

This looks very much with a issue for the nvidia toolkit, and probably not a container issue.

So this mean's I'm out of luck?

@j0nnymoe
Copy link
Member

Try reinstalling the plugin? Try an older driver version?

@Crylia
Copy link
Author

Crylia commented Mar 18, 2024

Try reinstalling the plugin? Try an older driver version?

I tried another jellyfin docker (bbergle-jellyfin) and it works fine.

Maybe its an ubuntu related problem? Since the other docker is using debian

@j0nnymoe
Copy link
Member

No issues here using jellyfin with Nvidia on unraid.

@Crylia
Copy link
Author

Crylia commented Mar 18, 2024

Probably something todo with my specific setup then, I'd close it for now as switching the docker fixed it for me.

@Crylia Crylia closed this as completed Mar 18, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants