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] intel igpu passthrough #54

Closed
1 task done
Mortezanavidi opened this issue May 4, 2024 · 3 comments
Closed
1 task done

[BUG] intel igpu passthrough #54

Mortezanavidi opened this issue May 4, 2024 · 3 comments

Comments

@Mortezanavidi
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

when i try to enable my intel igpu on the installation wizard, i get this error:

/wizard/index.js:79
  for (var i=0; i<imagesI.images.length; i++) {
                                 ^
TypeError: Cannot read properties of undefined (reading 'length')
    at setGpu (/wizard/index.js:79:34)
    at Socket.install (/wizard/index.js:115:23)
    at Socket.emit (node:events:517:28)
    at Socket.emitUntyped (/wizard/node_modules/socket.io/dist/typed-events.js:69:22)
    at /wizard/node_modules/socket.io/dist/socket.js:704:39
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
Node.js v18.20.2

becausee of this error installation doesn't even start

Expected Behavior

No response

Steps To Reproduce

get an intel igpu
try to enable it on the first page of wizard installation
check container logs

Environment

- OS: Ubuntu 22.04

CPU architecture

x86-64

Docker creation

services:
  kasm:
    image: lscr.io/linuxserver/kasm:latest
    container_name: kasm
    privileged: true
    devices:
      - "/dev/dri/card0:/dev/dri/card0"
      - "/dev/dri/renderD128:/dev/dri/renderD128"
    environment:
      - KASM_PORT=443
    volumes:
      - /home/user/docker/kasm/data:/opt
      - /home/user/docker/kasm/profiles:/profiles
    ports:
      - 3000:3000
      - 443:443
    networks:
      - kasm
    restart: unless-stopped

networks:
  kasm:
    external: true

Container logs

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    911
User GID:    911
───────────────────────────────────────
[custom-init] No custom files found, skipping...
[ls.io-init] done.
time="2024-05-04T21:42:56.446989749Z" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"
/wizard/index.js:79
  for (var i=0; i<imagesI.images.length; i++) {
                                 ^
TypeError: Cannot read properties of undefined (reading 'length')
    at setGpu (/wizard/index.js:79:34)
    at Socket.install (/wizard/index.js:115:23)
    at Socket.emit (node:events:517:28)
    at Socket.emitUntyped (/wizard/node_modules/socket.io/dist/typed-events.js:69:22)
    at /wizard/node_modules/socket.io/dist/socket.js:704:39
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
Node.js v18.20.2
Copy link

github-actions bot commented May 4, 2024

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

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Aug 3, 2024
Copy link

github-actions bot commented Sep 2, 2024

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

2 participants