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

Request / Call for help: Brasero #85

Open
MCOfficer opened this issue Dec 17, 2022 · 2 comments
Open

Request / Call for help: Brasero #85

MCOfficer opened this issue Dec 17, 2022 · 2 comments

Comments

@MCOfficer
Copy link

MCOfficer commented Dec 17, 2022

Firstly, thank you for your work on these GUI containers. I appreciate how many things you've already set up, and how easy it is (in theory) to create a new image for <insert random GUI application>.

Since I want to use my NAS drive for reading and writing, I set out to create such an image for Brasero, one of the more notorious burn applications on linux. I've made it past the gstreamer compilation, Brasero's asinine plugin version detection, but here's one final obstacle I cannot pass: Drives.

Brasero is rather similar to Handbrake, in that it seems to use gio to access drives. But unlike your handbrake container, the gio in my container just cannot find any disks:

❯ docker run --device /dev/sr0 --device /dev/sg0 --device /dev/sg1 -it jlesage/handbrake gio mount --list
Volume(0): cdrom
  Type: GUnixVolume
Volume(1): usb
  Type: GUnixVolume

❯ docker run --device /dev/sr0 --device /dev/sg0 --device /dev/sg1 -it my-brasero-container gio mount --list
# no output

The one difference I can see is that your container still uses the S6 overlay, so your init scripts look very different. But then I noticed that my test case, docker run, doesn't even execute the init scripts. So your container is just built different, and I cannot figure out why!

Also, there's a side-issue of sorts: Apparently the handbrake image (and mine, if it started working) only work with docker run, not docker compose: jlesage/docker-handbrake#236

So, that's where I stand right now. Do you have any pointers, or would you be willing to take over the brasero image entirely?

@jlesage
Copy link
Owner

jlesage commented Feb 13, 2023

I did a try on my side also and came with the same result as you: the drives are not detected.

MCOfficer added a commit to MCOfficer/brasero-docker that referenced this issue Feb 13, 2023
@MCOfficer
Copy link
Author

I had another idea while reading this, which turned out to be correct: it's the alpine version.

❯ docker run --device /dev/sr0 --device /dev/sg0 --device /dev/sg1 -it brasero-web-docker:alpine315 gio mount --list
Volume(0): cdrom
  Type: GUnixVolume
Volume(1): usb
  Type: GUnixVolume

❯ docker run --device /dev/sr0 --device /dev/sg0 --device /dev/sg1 -it brasero-web-docker:alpine316 gio mount --list

I'm not sure yet which package changed (probably glib) since I can't convince alpine to install something from edge when it's already in the current version's repos. But at least that's one mystery less, one that you would have come across sooner or later too.

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