Update documenation on Github and DockerHub to add privileged flag

[dantheman213]

Hello, I noticed the DockerHub image didn't work for me when I ran it as advised in the README.. after fiddling around I see you need to add the --privileged flag to get this to work. My final command looked like this:

docker run -d \
    --name=makemkv \
    -p 5800:5800 \
    -v /etc/makemkv/config:/config:rw \
    -v /opt/makemkv/storage:/storage:ro \
    -v /opt/makemkv/output:/output:rw \
    --device /dev/sr0 \
    --device /dev/sg2 \
    --restart=always \
    --privileged \
    jlesage/makemkv

Great DockerHub image btw.

[jlesage]

The--privileged option is not required, unless the container is misconfigured.
What is the problem exactly without the option? Did you adjust USER_ID and GROUP_ID ?

[RyanRoberts210]

QNAP? I can only make it work with Privileged selected otherwise it doesn't see the drive at all.

[jlesage]

Could you provide the container's log ?

[RyanRoberts210]

I believe this is what you are looking for. As you can see, it allows one of the two devices to be detected, enough for me to do what I need to do with it. I understand the limitations/complexities added by using Container Station on QNAP instead of using ssh and then something like yaml files, at least I think I do. I’m probably getting to the complexity point where I will switch someday and then maybe this gets better/easier. Thx From: Jocelyn Le Sage <[email protected]> Sent: Monday, May 25, 2020 5:05 PM To: jlesage/docker-makemkv <[email protected]> Cc: RyanRoberts210 <[email protected]>; Comment <[email protected]> Subject: Re: [jlesage/docker-makemkv] Update documenation on Github and DockerHub to add privileged flag (#74) Could you provide the container's log ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjlesage%2Fdocker-makemkv%2Fissues%2F74%23issuecomment-633747237&data=02%7C01%7C%7Cc5ff1bd7e9784323876408d801086165%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637260482785015233&sdata=JHRewEkXhX%2BUt5mf4Ue1wa3Bn4e9uyQ0Ych3gmRi6qc%3D&reserved=0>, or unsubscribe<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPVDBLECCNTFO53E2BG5IWDRTMBRLANCNFSM4M2DR3ZQ&data=02%7C01%7C%7Cc5ff1bd7e9784323876408d801086165%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637260482785025234&sdata=KoGdoN9B3fycfETtKFufT%2B90HiqSUqkoD1dESrl4A4k%3D&reserved=0>.

[jlesage]

Device files (e.g /dev/sr0) on QNAP have very restrictive permissions. They need to be adjusted manually. See #53.