[support] rix's Docker Repository


rix

Recommended Posts

On 1/28/2022 at 11:47 PM, NajChris11 said:

Yes, I understand. I was saying that I made a second container, routed it to the second optical drive, and yet for some odd reason both containers try to read from the first optical drive.

Did you have success with this? I've tried various mappings with docker parameters and I got it to see the other drive, but the directory structure was garbage on output. I tried modding the .sh file and that still was a problem. I've kind of given up on multiple disks and just use something else for bluray (separate drive).

@rixI think all of us need more specific instructions on how to get this to work with something other than sr0. Can you post an example of something like sr5/sg12 on the container syntax? I have tried with and without privileged, and I have used --device=/dev/sr5:/dev/sr0 \ --device=/dev/sg12:/dev/sg0 \ and --device=/dev/sr0:/dev/sr5 \ --device=/dev/sg0:/dev/sg12 \ and (I can't remember which one) one of them worked, but the output folder structure that led to the ripped files was all goofed.

Link to comment
On 1/21/2022 at 2:18 AM, rix said:

The Github readme clearly states you need to run one container per optical drive.

The commenter's post clearly states they made two containers.

 

I've tried all the methods to use 2 drives and 2 containers, but it always picks up the other drive. It is pulling the information from somewhere else. The creator only cares to support for $ 

Quote

Do you offer support?

Yes, but only for my sponsors. Not a sponsor - no support. Want to help yourself? Fork this repo and try fixing it yourself. I will happily review your pull request.

 

Link to comment
11 minutes ago, stayupthetree said:

The commenter's post clearly states they made two containers.

 

I've tried all the methods to use 2 drives and 2 containers, but it always picks up the other drive. It is pulling the information from somewhere else. The creator only cares to support for $ 

 

Good luck getting support for a passion project with that attitude ;)

Link to comment

so you do follow the thread, just don't care to help. Point proven. Being helpful to those seeking help would have probably lead you to the sponsors you complain about not having. 

 

Quote

How do I rip from multiple drives simultaneously?

Simple: run multiple containers of this image, passing through each separate drive accordingly.

 

Clearly false, or multiple people here wouldn't be asking for help on the issue. Going through your issues on github, you couldn't even be arsed to have abcde.conf easily accessible for people to edit. Majority of it is "I'd be happy to review a pull request". Why would anyone sponsor someone who wants other people to do the work they wont/cant do?

 

Just be honest, you either 1) don't want to help or 2) can't help because you likely didn't make 90% of this

 

Good luck getting sponsors for a passion project with that attitude. ;)

  • Haha 1
Link to comment
1 minute ago, stayupthetree said:

All one needs to do is look at your github issues and see you don't want to help people. This SPECIFIC issue is 2 years old. People tell you it isn't working. And you just go "Its in the readme". 

You do not seem to grasp the concept of "no support".

Link to comment

This just needs to calm down here @stayupthetree, @rix before it gets out of control.

 

The "tag" of Community Developer is not handed out like candy here, and after the initial round of giving this title (when the forum first supported it), it is actually fairly hard to come by and rarely given.

 

Being nasty or sarcastic isn't going to accomplish anything in this circumstance.  

 

Arguing by a dev of a container and a user between the various use cases for a container (that the author may have absolutely zero way to test or implement) isn't helpful.  As a general rule, all the authors / maintainers etc do everything for free in their spare time with no compensation at all.  @rix does appear at first glance to support his applications whether you are a sponsor or not.

 

That being said, it seems to me that because of how containers work there is absolutely no "real" reason why with proper mappings of the devices that multiple instances each with a separate drive mapped to them wouldn't work.  I am however also completely unable to replicate any such situation, as I haven't seen a need for any optical drive installed on any system I own (server or otherwise) in over 10 years, so can't say for sure either way.

 

This app was initially added to CA January 13, 2017 and the latest update was 7 days ago, so the application is obviously still supported and not abandoned 

 

 

  • Thanks 2
Link to comment
15 minutes ago, Squid said:

This just needs to calm down here @stayupthetree, @rix before it gets out of control.

 

The "tag" of Community Developer is not handed out like candy here, and after the initial round of giving this title (when the forum first supported it), it is actually fairly hard to come by and rarely given.

 

Being nasty or sarcastic isn't going to accomplish anything in this circumstance.  

 

Arguing by a dev of a container and a user between the various use cases for a container (that the author may have absolutely zero way to test or implement) isn't helpful.  As a general rule, all the authors / maintainers etc do everything for free in their spare time with no compensation at all.  @rix does appear at first glance to support his applications whether you are a sponsor or not.

 

That being said, it seems to me that because of how containers work there is absolutely no "real" reason why with proper mappings of the devices that multiple instances each with a separate drive mapped to them wouldn't work.  I am however also completely unable to replicate any such situation, as I haven't seen a need for any optical drive installed on any system I own (server or otherwise) in over 10 years, so can't say for sure either way.

 

This app was initially added to CA January 13, 2017 and the latest update was 7 days ago, so the application is obviously still supported and not abandoned 

 

 

Thanks for chiming in so quickly, @squid.

 

I have decided not to respond to hostile comments. I am less than willing to spend my free time on internet trolls.

 

To clear things up: as per https://github.com/rix1337/docker-ripper#do-you-offer-support I happily am able to confirm, I am not able to offer any support on this issue. Transparency is always important in open source projects - that's why that passage was added to the readme.

 

Ripper generally works well and anyone is free to solve issues and improve the project by sending a pull request.

 

@stayupthetree if you need further assistance and do not want to become a sponsor, then you can either:

a) ask others in the community how they managed to get multiple drives working

b) ship me a secondary optical drive for free (ideally your exact model) so I can try and diagnose this

 

Edit: To further facilitate transparency I have reworded the https://github.com/rix1337/docker-ripper/blob/master/README.md#how-do-i-rip-from-multiple-drives-simultaneously section in Ripper's readme. ;)

Edited by rix
  • Haha 1
Link to comment

Thanks for chiming in so quickly, @squid. I am not willing to spend my free time with internet trolls. I will suggest tho that with sponsorships, usb dvd drives are fairly cheap on Amazon. Here's what I can say. After extensive testing, I wiped all remnants of Ripper off the server. Reinstalled removing the extra paramenter for device passthrough. I then consoled into the container and ran the command used inside ripper.sh to get the status of the drive. Here is my result. Perhaps someone here can explain how with zero devices passed through to the container, the container still shows both drives?

 

 

[email protected]:/# makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
DRV:0,1,999,0,"DVD+R-DL hp DVDRAM GT20L DC05 KW29COA4542","","/dev/sr0"
DRV:1,1,999,0,"DVD+R-DL Memorex MRX-650LE v7 1.00 SSG1B02846","","/dev/sr1"
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""

 

Link to comment
2 minutes ago, stayupthetree said:

Perhaps someone here can explain how with zero devices passed through to the container, the container still shows both drives?

 

That's where I got to with it. I couldn't understand how it was seeing sr0 as sr0 still when I intentionally tried to map it to a different sr(x) for testing purposes. This docker works excellent with one drive. My server has one built-in (laptop style) dvd burner. I have a usb bluray burner. In order to rip blurays I have to use the makemkv docker or a vm or my w10 laptop. I could never get ripper to ignore sr0 and go for the external. Mapping sr5 (external burner) to sr0 caused it to try to read from both drives simultaneously. I've been dabbling with Linux since 1999 Redhat 5.2, but only really got stuck in firm last year so I'm just chalking it up to my own inexperience. I can follow complex directions, but I need more directions.

Link to comment
4 hours ago, stayupthetree said:

the container still shows both drives?

The reason the container can see both drives is if the docker is running in priviledged mode it has complete access to all devices, so will ignore the device statements. I dont know any other effects of turning off privileged mode with the docker. @rix DM me if you want me to to any testing for you.

 

image.thumb.png.434660f9128def71c273226038ed7add.png

 

# makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
DRV:0,0,999,0,"BD-RE ASUS BW-16D1HT 3.01 SIK9GH6KA463","","/dev/sr0"
DRV:1,0,999,0,"BD-RE HL-DT-ST BD-RE BU40N 1.03 MZUJ5KF3531","","/dev/sr1"
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
TCOUNT:0
# 

 

 

 

image.thumb.png.9f237f284b1f18b07b61c13e71ad4da7.png

 

# makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
DRV:0,0,999,0,"BD-RE HL-DT-ST BD-RE BU40N 1.03 MZUJ5KF3531","","/dev/sr1"
DRV:1,256,999,0,"","",""
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
TCOUNT:0
# 

 

Link to comment
2 minutes ago, SimonF said:

The reason the container can see both drives is if the docker is running in priviledged mode it has complete access to all devices, so will ignore the device statements. I dont know any other effects of turning off privileged mode with the docker. @rix DM me if you want me to to any testing for you.

 

image.thumb.png.434660f9128def71c273226038ed7add.png

 

# makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
DRV:0,0,999,0,"BD-RE ASUS BW-16D1HT 3.01 SIK9GH6KA463","","/dev/sr0"
DRV:1,0,999,0,"BD-RE HL-DT-ST BD-RE BU40N 1.03 MZUJ5KF3531","","/dev/sr1"
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
TCOUNT:0
# 

 

 

 

image.thumb.png.9f237f284b1f18b07b61c13e71ad4da7.png

 

# makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
DRV:0,0,999,0,"BD-RE HL-DT-ST BD-RE BU40N 1.03 MZUJ5KF3531","","/dev/sr1"
DRV:1,256,999,0,"","",""
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
TCOUNT:0
# 

 

 

That makes sense. It's one of the reasons why the privileged flag is not part of the default config in the Readme.

 

Some users were unable to use ripper without the flag though so it's usefulness may differ between various use cases.

 

So what you are saying is it works for you if you don't run the container as privileged?

Link to comment
40 minutes ago, rix said:

So what you are saying is it works for you if you don't run the container as privileged?

I have only tested the commands in my post to show it only finds the one dev with priv turned off. I have not ripped any discs as I have not completed the setup so cannot confirm at this point if it works correctly with priv turned off.

 

I will look at the setup and see if I can test further

Edited by SimonF
  • Thanks 1
Link to comment
1 hour ago, rix said:

So what you are saying is it works for you if you don't run the container as privileged

It is ripping a Blue Ray in non priv mode. Created two containers, second one found disk, but issue is my drive does funny things if not used for a while and needs to be reset hence the disk still loading and not able to reboot my server to fix, but looks like it should work as expected. Will test CD on the one ripping to confirm also.

 

image.thumb.png.89b62ee7f2f820d08b96eec286934ffa.png

Edited by SimonF
Link to comment
1 hour ago, SimonF said:

It is ripping a Blue Ray in non priv mode. Created two containers, second one found disk, but issue is my drive does funny things if not used for a while and needs to be reset hence the disk still loading and not able to reboot my server to fix, but looks like it should work as expected. Will test CD on the one ripping to confirm also.

 

image.thumb.png.89b62ee7f2f820d08b96eec286934ffa.png

 

Sounds good. Thanks for investing your free time to help others.

Link to comment

After the recent ungrateful comments and hostility I have decided to unfollow the thread starting with this post to not post on this forum anymore - this includes DMs (exceptions will be made for the Unraid/Mod team).

Github issues / discussions are still welcome - and allow me to moderate what I spend my precious free time on.

 

Feel free to discuss my work here and help each other out - so no need to lock this thread. This has worked well in the past.

 

I will continue to work on my projects and publish them (also to the Unraid template repo), for people who find them useful.

 

EDiT: I have removed all links to this thread from my template repo.

Edited by rix
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.