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

debian/ubuntu may need privileged to share /dev/dri, crashes on chromebook without it #566

Open
ericcurtin opened this issue Jan 10, 2025 · 11 comments

Comments

@ericcurtin
Copy link
Collaborator

No description provided.

@rhatdan
Copy link
Member

rhatdan commented Jan 10, 2025

Privileged container or to run as root?

@ericcurtin
Copy link
Collaborator Author

I think the fix for this is just to add a "--privileged" option to RamaLama for these kinda platforms.

@ericcurtin
Copy link
Collaborator Author

The ChromeOS Linux environment is a Debian-based environment and needs this. To be fair the ChromeOS environment is:

ChromeOS Linux Distro->crosvm->some other Linux Distro->lxc/lxd->Debian->podman (via RamaLama)->ubi9

so it's a lot of layers, but it works! Sometimes it needs "--privileged" and sometimes it doesn't oddly enough (today it's fine, but other days I boot it up and it needs "--privileged" to access /dev/dri).

@ericcurtin
Copy link
Collaborator Author

It's probably a ChromeOS bug at the root, but still a --privileged option would do no harm, always off by default

@ericcurtin
Copy link
Collaborator Author

It's a rootless podman container I was using on ChromeOS

@ericcurtin
Copy link
Collaborator Author

ericcurtin commented Jan 10, 2025

We will actually be Android compatible in the next release of Android also

@ericcurtin
Copy link
Collaborator Author

Google are currently porting this Linux guest VM ChromeOS environment to Android

@ericcurtin
Copy link
Collaborator Author

#572

@rhatdan
Copy link
Member

rhatdan commented Jan 13, 2025

Not sure why this would be fixed by --privileged. We already disable SELinux.

The only reason that I know of for /dev/dri not being accessible would be DAC (UID/Permissions) not being correct, and --privileged would not fix this.

If we got into this situation, I would like to debug what is actually the problem.

@ericcurtin
Copy link
Collaborator Author

Not sure why this would be fixed by --privileged. We already disable SELinux.

The only reason that I know of for /dev/dri not being accessible would be DAC (UID/Permissions) not being correct, and --privileged would not fix this.

If we got into this situation, I would like to debug what is actually the problem.

It maybe ChromeOS-specific, --privileged does fix it, whatever it is. Anything I should paste here next time I see it?

@rhatdan
Copy link
Member

rhatdan commented Jan 13, 2025

I would want to see the ownership of /dev/dri
ls -lZ /dev/dri

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants