-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
/dev/sr0 permissions #3
Comments
You need to detect at runtime (via an init script) the group of the device. This group will become a supplementary group of You can look at https://github.com/jlesage/docker-handbrake/blob/master/rootfs/etc/cont-init.d/95-check-optical-drive.sh for an example. |
Weird, so I added |
Using only the script is sufficient. No need to manually sets |
Got it working now thanks! Once I get it up on here would you mind casting your eyes over it to see if there's anything I could improve? One last question, the final output on stdout I get from my app is this;
Is this something to worry about as the app looks fine and works fine too :) |
Sure I can have a look. I would not worry about the error. Seems to occur eith xvfb. |
Thanks for the note on the error. Repo is b3vis/docker-dvdisaster |
Hi,
I'm trying to correct an issue I've got using this image as a base for a piece of software called dvdisaster. I've managed to get all the build working but I'm struggling with the permissions to /dev/sr0. On the docker host my user with id 1000 is a member of the cdrom group which has
rw
on /dev/sr0 on my host but theapp
user inside the container isn't able to access sr0 from my host.I have then
docker exec
'd into the container and doneusermod -aG cdrom app
and reloaded the app and it's then able to access /dev/sr0. I've tried adding the usermod to my Dockerfile but I think this user is made on container start.Any tips?
Thanks,
b3vis
P.S I tried to look through your MakeMKV container to see how you've solved this on that image but was unable to see anything obvious
The text was updated successfully, but these errors were encountered: