July 17, 20178 yr Author Yes it does have java installed. It is also needed to get around certain copy protections.However, I was not able to test it, since I don't have a proper Bluray that would need java.MakeMKV should find Java location automatically.Are you able to test it to see if it's working?
July 18, 20178 yr 2 hours ago, Djoss said: Yes it does have java installed. It is also needed to get around certain copy protections. However, I was not able to test it, since I don't have a proper Bluray that would need java. MakeMKV should find Java location automatically. Are you able to test it to see if it's working? i don't currently have a screenpass protected disc either
July 23, 20178 yr The docker seems to be broken after an update. This is the docker log. (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] openbox: waiting for xvfb to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error:
July 23, 20178 yr 1 minute ago, Djoss said: It is not starting? Do you have the whole log since the beginning? services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready... [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] xvfb: starting... (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) [services.d] app: waiting for openbox to be ready... [services.d] x11vnc: waiting for xvfb to be ready... [services.d] openbox: waiting for xvfb to be ready...
July 24, 20178 yr Author Can you try to remove the /tmp/.X0-lock file from the container? This can be done with this command (to run on your unraid server): docker exec MakeMKV rm /tmp/.X0-lock
July 24, 20178 yr 21 hours ago, Djoss said: Can you try to remove the /tmp/.X0-lock file from the container? This can be done with this command (to run on your unraid server): docker exec MakeMKV rm /tmp/.X0-lock Thank you
July 24, 20178 yr Author 4 minutes ago, deaerator said: Thank you So it did fix the issue? In this case I will add some enhancements to make sure this situation doesn't occur again.
July 27, 20178 yr Author @deaerator, did you restarted/updated the container since you fixed the issue? If not, could you provide the output of: docker exec MakeMKV ps -A Thanks!
July 27, 20178 yr 15 minutes ago, Djoss said: @deaerator, did you restarted/updated the container since you fixed the issue? If not, could you provide the output of: docker exec MakeMKV ps -A Thanks! Output
July 31, 20178 yr Hello, Just to say THANK YOU for this work. This container works great on my server, especially the stream capability. It has been years I wanted to build my own video disc player without the need to rip, transcode or convert ... just put the disc and play it freely with all the devices connected to my network. Good job.
August 24, 20178 yr Hello... I just wanted to say thanks for providing this docker, it was easy to install and works like a dream!
September 11, 20178 yr Hello all, I have what I presume to be a very noob question, but I just switch to Unraid from Ubuntu and am having trouble getting this docker application to work properly (most likely an issue with me doing something wrong). The application itself is able to run, and decode the disc displaying all the titles available on the disc, however when I select the title(s) I want to make into mkvs and click the save selected titles button, if will do the analysis, but then error out with "Error 'Posix error - Read-only file system' occurred while creating '/storage/MKVOutput/title_name'" I know that this is a permissions issue, but I have not been able to find a solution to this problem. Some useful information: I am using the Webgui over my intranet. I am logged in as root on the webgui. The share that it is set to write to is currently set to public. I would prefer to continue to use the webgui for makemkv as it is easier for other people to use. If someone could provide some help that would be amazing. Thanks in advance
September 11, 20178 yr With @Djoss 's Handbrake docker utilizing 5800 and 5900, does running this docker at the same time create a conflict? EDIT: Or I assume this is a internal docker port vs external Unraid port? I assume the Unraid layer will create it's own published port for the app, and the Docker engine will keep track? Edited September 11, 20178 yr by cybrnook
September 11, 20178 yr 49 minutes ago, Thunderwolf123 said: Hello all, I have what I presume to be a very noob question, but I just switch to Unraid from Ubuntu and am having trouble getting this docker application to work properly (most likely an issue with me doing something wrong). The application itself is able to run, and decode the disc displaying all the titles available on the disc, however when I select the title(s) I want to make into mkvs and click the save selected titles button, if will do the analysis, but then error out with "Error 'Posix error - Read-only file system' occurred while creating '/storage/MKVOutput/title_name'" I know that this is a permissions issue, but I have not been able to find a solution to this problem. Some useful information: I am using the Webgui over my intranet. I am logged in as root on the webgui. The share that it is set to write to is currently set to public. I would prefer to continue to use the webgui for makemkv as it is easier for other people to use. If someone could provide some help that would be amazing. Thanks in advance Make sure you are putting the files in the UNRAID directory (when you are inside of MakeMKV) otherwise MakeMKV doesn't have permissions to write outside. When you installed the container you gave it a path to write to **EXAMPLE** Host: /mnt/user/Media Container: /UNRAID When you are inside the container "/UNRAID" is mounted/pointed to "/mnt/user/Media" <--- The physical location in the array. if you don't select the directory "/UNRAID" you'll get permission errors. Edited September 11, 20178 yr by MowMdown
September 11, 20178 yr 13 minutes ago, MowMdown said: Make sure you are putting the files in the UNRAID directory (when you are inside of MakeMKV) otherwise MakeMKV doesn't have permissions to write outside. When you installed the container you gave it a path to write to **EXAMPLE** Host: /mnt/user/Media Container: /UNRAID When you are inside the container "/UNRAID" is mounted/pointed to "/mnt/user/Media" if you don't select the directory "/UNRAID" you'll get permission errors. @MowMdown Thanks for the help, this wasn't the exact solution, but lead me to it. It seems for whatever reason the storage directory was set correctly, but access mode under advanced edit was set to read instead of read/write. After changing it to read/write it is now working. Thank you for the help.
September 11, 20178 yr Author 1 hour ago, Thunderwolf123 said: It seems for whatever reason the storage directory was set correctly, but access mode under advanced edit was set to read instead of read/write. After changing it to read/write it is now working. /storage is intended to be read only, as this is the source for video files. /output is where converted videos should be saved.
September 11, 20178 yr Author 2 hours ago, cybrnook said: With @Djoss 's Handbrake docker utilizing 5800 and 5900, does running this docker at the same time create a conflict? EDIT: Or I assume this is a internal docker port vs external Unraid port? I assume the Unraid layer will create it's own published port for the app, and the Docker engine will keep track? Yes, ports 5800 and 5900 are ports "inside" the container. They are mapped to ports on the host and each container has a different mappings (so no conflict).
September 11, 20178 yr 1 minute ago, Djoss said: /storage is intended to be read only, as this is the source for video files. /output is where converted videos should be saved. Hi @Djoss while I understand this, for whatever reason I needed to change the setting on source for it to work. Could this have to do with me installing the application first without privilege enabled, then enabling it later on? From what I understand /output will inherit /storage permission's if /storage has greater permissions, could /output have been set to read only and changing /storage changed /output to read/write?
September 11, 20178 yr Author /storage and /output are independent. You can configure read/write permissions off both in container's settings, so permissions of one should not affect the other. But the error "Error 'Posix error - Read-only file system' occurred while creating '/storage/MKVOutput/title_name'", indicates that the file is being saved under /storage, while it should be saved under /output...
September 11, 20178 yr On 6/27/2017 at 7:13 AM, Djoss said: Same thing as an internal drive. In my case, the device is /dev/sr0, so I just add --device /dev/sr0 in extra parameters. Sorry if it's not spelled out. If I want to add either a USB drive, or SATA drive, I would add the path here (add another path, port or variable, and choose device?)?
September 11, 20178 yr @cybrnook Tick the "Advanced View" in the upper right corner, and you'll see an "Extra Parameters" section just below the "Description" section once your device is plugged into the machine, find its device id/path. cd into /dev/disk/by-id then run ls -l then figure out which is the USB/Device you need - see below on the far right. root@Tower:/dev/disk/by-id# ls -l total 0 lrwxrwxrwx 1 root root 9 Sep 7 16:46 ata-ASUS_DRW-24B1ST_c_C1D0CL043771 -> ../../sr0 lrwxrwxrwx 1 root root 9 Sep 7 16:46 ata-WDC_WD6400AAVS-00G9B0_WD-WCAUF0537940 -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 7 16:46 ata-WDC_WD6400AAVS-00G9B0_WD-WCAUF0537940-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Sep 7 16:46 usb-PNY_USB_2.0_FD_4530100578919190-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 7 16:46 usb-PNY_USB_2.0_FD_4530100578919190-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Sep 7 16:46 wwn-0x10770454365260107777x -> ../../sdb lrwxrwxrwx 1 root root 10 Sep 7 16:46 wwn-0x10770454365260107777x-part1 -> ../../sdb1 so lets say I wanted to add a device like my CD-DVD drive (obviously not a storage device) I would add in the extra parameters section --device /dev/sr0 Hit Save
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.