Coder Social home page Coder Social logo

Comments (29)

derekbsnider avatar derekbsnider commented on August 13, 2024 1

@briandaymsft I never got it working, but I didn't end up trying the last few things recommended (modifying /dev/sr0 /dev/sg4 permissions, etc). I wasn't sure if it was just the type of drive I'm using is not compatible with the QNAP hardware, but I'm up for trying again.

I would really like to be able to rip directly to the QNAP if possible, as it would reduce any network bottlenecks, and I was hoping to set things up to just be able to put a DVD or BluRay into the drive, have it automatically rip it, and open the drive when complete, so it was completely automated (aside from interaction with the physical discs).

from docker-makemkv.

jlesage avatar jlesage commented on August 13, 2024

Is it only for the optical drive part that you need help with? Are you able to create the container and access to UI of MakeMKV?

from docker-makemkv.

derekbsnider avatar derekbsnider commented on August 13, 2024

Yes, I can create the container and access the UI -- It says that no optical drive was found.

from docker-makemkv.

jlesage avatar jlesage commented on August 13, 2024

Ok, so the problem is probably that you didn't exposed the required devices to the container.
If you look at the container's log, you should see messages telling that your drive is detected but is not working. Messages will also tell you which devices to expose.

from docker-makemkv.

derekbsnider avatar derekbsnider commented on August 13, 2024

Do you know how to expose the device using QNAP's "Container Station"?

from docker-makemkv.

jlesage avatar jlesage commented on August 13, 2024

I don't have a QNAP to look at, but if you edit container's settings, I think there is a "Device" section.

from docker-makemkv.

RyanRoberts210 avatar RyanRoberts210 commented on August 13, 2024

Today, in Container Station, Settings, Advanced Settings, Device, there is a drop down menu with 5-6 choices. I can get the drive recognized enough by choosing Input and setting the Privileged checkbox. This allows the container to see it (sg# only) and for me to rip with it. The auto-eject does not work.

from docker-makemkv.

derekbsnider avatar derekbsnider commented on August 13, 2024

Today, in Container Station, Settings, Advanced Settings, Device, there is a drop down menu with 5-6 choices. I can get the drive recognized enough by choosing Input and setting the Privileged checkbox. This allows the container to see it (sg# only) and for me to rip with it. The auto-eject does not work.

How do you actually mount the drive inside the container?

from docker-makemkv.

RyanRoberts210 avatar RyanRoberts210 commented on August 13, 2024

If you follow those steps during your container setup this "mounts" the drive in the container, i.e. makes it accessible to the container. You should see it detected in the Console of Container Station when it starts up the container. This all assumes you are using Container Station to setup the container and not ssh or something else.

from docker-makemkv.

derekbsnider avatar derekbsnider commented on August 13, 2024

from docker-makemkv.

RyanRoberts210 avatar RyanRoberts210 commented on August 13, 2024

from docker-makemkv.

derekbsnider avatar derekbsnider commented on August 13, 2024

from docker-makemkv.

RyanRoberts210 avatar RyanRoberts210 commented on August 13, 2024

from docker-makemkv.

jlesage avatar jlesage commented on August 13, 2024

Could you provide the output of:

ls -l /dev/

and

docker exec <name of the container> lsscsi -g -k

from docker-makemkv.

derekbsnider avatar derekbsnider commented on August 13, 2024

from docker-makemkv.

JSeluga avatar JSeluga commented on August 13, 2024

Did this ever get figured out on a QNAP device. I am running into the same issues.

from docker-makemkv.

J-miahL avatar J-miahL commented on August 13, 2024

The only way I am able to expose the drive is in privilege mode, and running and stopping the container once prior to connecting the drive. I modified the permission for both sr0 and sg4 to R-X for everyone. The UID and GUID is setup to user/everyone not admin/administration. It might just be a QNAP limitations, since I have another container that requires privilege mode to expose the render for hardware acceleration.

from docker-makemkv.

briandaymsft avatar briandaymsft commented on August 13, 2024

Did this ever get figured out on a QNAP device. I am running into the same issues.

I am also curious if @derekbsnider figured out a way as I'm faced with pretty much the same issue now. For all intents and purposes, it appears the device is exposed to my container, but MakeMKV itself doesn't find it.

from docker-makemkv.

briandaymsft avatar briandaymsft commented on August 13, 2024

Thanks for the update @derekbsnider , I'm going through some of the same steps over here, #160, so if I find anything that works I'll share it.

from docker-makemkv.

J-miahL avatar J-miahL commented on August 13, 2024

from docker-makemkv.

briandaymsft avatar briandaymsft commented on August 13, 2024

For less advance users, boot the NAS first and then plug in the drive. After that you can create a privilege container. I don't remember if you have to select anything under device, but you may need to expose USB devices. The container should see the device. Note you must re-plug the drive if the container is stopped for any reason prior to restarting the container.

So far, I've not seen any change in behavior when making it a privileged container. Maybe my sequence of events is off. I could try it again just to see if I can force it, but I'd prefer to not run privileged if I can. Even if it would show up once while privileged it would give me hope there's a way to make it work perhaps with your other method. :)

from docker-makemkv.

briandaymsft avatar briandaymsft commented on August 13, 2024

So far, I've not seen any change in behavior when making it a privileged container. Maybe my sequence of events is off. I could try it again just to see if I can force it, but I'd prefer to not run privileged if I can. Even if it would show up once while privileged it would give me hope there's a way to make it work perhaps with your other method. :)

I tried again with --privileged and not specifying any --device values, and I tried with --privileged and the two --device values, still nothing. Really odd. I'll try the permissions method sometime tomorrow.

from docker-makemkv.

J-miahL avatar J-miahL commented on August 13, 2024

from docker-makemkv.

derekbsnider avatar derekbsnider commented on August 13, 2024

Are you setting up the container via terminal or using the Container App? The first method can only be done via terminal.

Could you please provide details on how to properly set this up and get it working via the terminal?

Thank you! :)

from docker-makemkv.

J-miahL avatar J-miahL commented on August 13, 2024

from docker-makemkv.

J-miahL avatar J-miahL commented on August 13, 2024

from docker-makemkv.

briandaymsft avatar briandaymsft commented on August 13, 2024

Are you setting up the container via terminal or using the Container App?

I'm doing it via SSH. My trials and tribulations are over in #160 , not trying to detail this one tooooo much. :)

from docker-makemkv.

briandaymsft avatar briandaymsft commented on August 13, 2024

For the more advanced user, I would recommend setting up a shell and giving rw permissions to the /dev/srx and /dev/sgy that corresponds to the drive. Make sure the user running the container is the same as the user or part of the group granted rw access. Then make sure you expose the device with the - device variable when setting up the container. Notes these permission erase upon reboot.

I now have initial success, @J-miahL. Based on your tip above it got me going in the proper direction. :)

Here are my /dev permissions for the necessary devices (for my setup) are currently, so only the 'admin' account has access and nobody else.

crw------- 1 admin administrators 21, 4 2023-01-23 10:01 sg4
brw------- 1 admin administrators 11, 0 2023-01-23 10:02 sr0

I created a container with the following command via shell, and for the first time specified zero for both USER_ID and GROUP_ID given what I saw above to see if it behaves any different. I'll change this later once I figure out the magic combo so the container isn't running as admin.

docker run -d --name=MakeMKV-2 -p 5800:5800 -v /docker/appdata/makemkv:/config:rw -v /share/Movies/:/output:rw --device /dev/sr0 --device /dev/sg4 -e USER_ID=0 -e GROUP_ID=0 jlesage/makemkv

With the above command, boom, MakeMKV sees my USB ASUS drive and ripped on the first try. 👍🏻

Now I should just have to go back and setup the permissions appropriately with a user other than admin. :) Thank you!

from docker-makemkv.

J-miahL avatar J-miahL commented on August 13, 2024

from docker-makemkv.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.