Unable to deploy in Docker/Truenas

[akavintz]

Hi All,
I am new to docker and github! Im trying to deploy this on my Truenas server but the image just sticks at "Deploying"
I created a custom app and specified the name as docker-makemkv, the repository as https://github.com/jlesage/docker-makemkv.git and I think that was it.
It looked promising, created an app but it wont start.
Im sure this is basic stuff but like I said, im a total newby to this.
Any advice?
Vince

[jlesage]

I'm not a user of Truenas, but usually the repository means the one on Docker hub (https://hub.docker.com/r/jlesage/makemkv), where the image is actually stored, not the GitHub repository.

[akavintz]

Hi and Thanks, Do you know what this means?
2024-02-08 16:25:57
Failed to apply default image tag "https://hub.docker.com/r/jlesage/makemkv:default": couldn't parse image reference "https://hub.docker.com/r/jlesage/makemkv:default": invalid reference format

[jlesage]

Can you share how you configured the container ? I think for Image Repository, you just need to enter jlesage/makemkv.

[akavintz]

Yes, I created a custom app and filled in these details as per the screenshots. Hopefully they all come through.







I do have the option to add a catalog!

Thanks for all your help :)

Vince

[C4Wiz]

image tag should be latest not default

[akavintz]

Thanks C4Wiz, I changed it but it still wont deploy. :(

[C4Wiz]

Sounds like a TrueNAS issue! This docker is flawless with unraid! Try asking in the TrueNAS forum

[jlesage]

I think Image Repository should be jlesage/makemkv.

[akavintz]

Thanks Jocelyn, that got it from deploying to running. Time to configure directories and devices now. Thanks for your help.

Vince

[akavintz]

Sorry to be a nuisance but what should I put in the command and argument fields?
Should I put docker run -d \ --name="thenameofmyapp" in command and then
-p 5800:5800
-v /mnt/Data2/makemkv:/config:rw
-v /home/user:/storage:ro
-v /mnt/Data2/makemkv/output:/output:rw
--device /dev/sr0
--device /dev/sg2
jlesage/makemkv
in seperate arguments?
Also should Iose the back slashes?
V

[jlesage]

I guess these fields are not needed.

The command you are pointing to (docker run ...) is not relevant in your case, since you are using a UI to configure/create containers. This command is used by people that create contains via cli.

[C4Wiz]

Sorry to be a nuisance but what should I put in the command and argument fields? Should I put docker run -d \ --name="thenameofmyapp" in command and then -p 5800:5800 -v /mnt/Data2/makemkv:/config:rw -v /home/user:/storage:ro -v /mnt/Data2/makemkv/output:/output:rw --device /dev/sr0 --device /dev/sg2 jlesage/makemkv in seperate arguments? Also should Iose the back slashes? V

I feel like you should be asking in the Truenas forum, they would know better how to deploy a docker on their OS

[akavintz]

They have their own repoisitory and one of the apps in their is Handbrake. The knowledge around custom deployments seems limited to none and as I really like makemkv I wanted to get this solution to work, if possible, if not I will move over to Handbrake.

Thanks though for your feedback.

[C4Wiz]

why not install the trial of unRAID and see what a real NAS OS is all about!

[jlesage]

I agree, so easy to use, especially for deploying/configuring Docker containers!

[akavintz]

I had a break through tonight and have got it working.
Once I got into the shell of the container and found the commands I needed to troubleshoot network and devices it took about five mins.
Sorry for asking stupid questions and troubling you with an unknown system but I do appreciate the feedback.
Vince

[jlesage]

Glad to hear that it's now working for you.

[gmensching]

I had a break through tonight and have got it working. Once I got into the shell of the container and found the commands I needed to troubleshoot network and devices it took about five mins. Sorry for asking stupid questions and troubling you with an unknown system but I do appreciate the feedback. Vince

How did you resolve it? I'm having the same issue in Truenas

[akavintz]

Hi, sorry for the delay in responding.
Honestly I dont remember, I built a nas in Jan and found rather than rip disks on my laptop I could do it direct on the nas with this docker app spent a few weeks messing about getting to going and then ripped all my disks boxed them up and switched off the nas to decorate and havent touched it since. I think it was network ip related and port but I honestly dont remember now. Sorry. If I can ill power it up in the next couple of days and see if anything jogs my memory. V

[gmensching]

Hi, sorry for the delay in responding. Honestly I dont remember, I built a nas in Jan and found rather than rip disks on my laptop I could do it direct on the nas with this docker app spent a few weeks messing about getting to going and then ripped all my disks boxed them up and switched off the nas to decorate and havent touched it since. I think it was network ip related and port but I honestly dont remember now. Sorry. If I can ill power it up in the next couple of days and see if anything jogs my memory. V

OK thank you. I'm just finding it equally frustrating to figure this out. Not much documentation on this and no resolutions in the forums.

[IDtheTarget]

This is from the notes I took when working through this. I hope they help:
(updated on 11/29/2024 to include configuration persistence)

Problem

Get instance(s) of MakeMKV running in TrueNAS Scale Electric Eel, with two Blu-Ray players, able to rip DVD/Blu-Ray to TrueNAS media pool. Not interested in automatic rip, I prefer to detail what I'm ripping in the WebUI before starting the rip process. The update process should be painless, specifically retaining the MakeMKV key that I purchased from update to update.

Description

I was running two instances of MakeMKV on TrueNAS Scale Cobia using True Charts apps. When I upgraded to Electric Eel, they went away. I have two Blue Ray players attached to my TrueNAS server via USB to speed up ripping TV shows since they always have multiple disks.

With Electric Eel, iX Systems moved away from Kubernetes and to Docker, which should be easier to deal with from what I'm reading online. I have very little experience with Docker, so this experience will be "Discovery Learning".

I have issues with my memory, so this document has two purposes. First so that I can document what I did for myself if I need to re-create it or describe my issues while asking for help. Second so that I can post and others may benefit from my journey.

Note: As previously mentioned, I have memory issues. So the steps I take will be more detailed than may otherwise be normal.

Disclaimers

1. I own all my disks. I purchase the disks, rip them to my Emby server, then store them in large Disk Cases. I purchase the disks because I believe that the people who created the content I like deserve to be compensated for their work. I retain the disks because that means I'm just changing how I view the content I've purchased, not pirating anything.
2. The below steps are what worked for me at the time I set this up. Use these steps at your own risk. I offer them only to help others who are trying to figure out how to solve the same problem I was faced with, and acknowledge zero liability. You could lose all your media and even your server, so look at these instructions with skepticism and critical though.

Environment

• Home-brew server with the following hardware:
  • SuperMicro X12STH-F-LN4F motherboard
  • Intel(R) Xeon(R) E-2356G CPU (I wanted a CPU with QSV for transcoding
  • 64GB ECC RAM (can't remember the brand, but I don't want to shut down the server to look)
  • ASUS Dual NVIDIA GeForce RTX 3060 V2 OC Edition 12GB (the QSV wasn't working in Emby the way I wanted)
  • Eight Seagate Exos X16 14TB 7200 RPM drives (and BOY are they noisy) (I wanted WD Red Pro drives, but got a sale on the Seagates, which were data-center grade)
  • Two custom Blu-Ray players that work with MakeMKV (see their forums if you need drives)
• TrueNAS Scale 24.10.0.2 (Electric Eel). I was running Cobia but was starting a new project for home cameras involving frigate and home assistant (don't ask yet, I haven't figured everything out). I decided that Cobia was nearing end-of-life, so if I was going to start a major (to me) new project, I should upgrade the server first and get it to the latest version. I upgraded to Dragon Fish then to Electric Eel. I knew I was going to lose MakeMKV and the other TrueCharts apps I'd been running, but it was worth it to me to ensure that the OS would continue to be supported. This is relevant to this document because, in my server admin experience, systems with OS's that have received multiple upgrades occasionally exhibit oddities that are not present with a fresh install. So things I may have had to deal with may not apply to you.

Process

First I did a search for "TrueNAS Scale Electric Eel MakeMKV" and came up with this: https://www.truenas.com/community/threads/custom-app-help-please-makemkv.116426/. It was a request from "akaVintz" for help with this very problem, with no replies. However, it lead to this: #197, which was some help. It also lead to a Docker container with MakeMKV here: https://github.com/jlesage/docker-makemkv so that's where I'm going to start.

Create a dataset for config persistence

I don't like having to re-configure the app everything it restarts or updates. So I'm creating a dataset in the main pool to hold my configs. I do this for most of my apps.

1. On the left of the UI, click on "Datasets"
2. In the "Datasets" section, make sure the pool you want to use is selected. Mine is "main_pool"
3. At the top right, click "Add Dataset"
4. In the "Name", put in what you want to use for configs. I used "configs".
5. Click the "Save" button
6. Select the "config" dataset you just created
7. At the top right, click the "Add Dataset" button again.
8. Make sure you see "main_pool/configs" in the "Parent Path" section.
9. In the "Name" field, put the name of your app container. I used "docker-makemkv"
10. Click the "Save" button

Install the Docker app

1. Log into the TrueNAS WebUI (https://<IP_address>:444/ui/dashboard)
2. On the left, click on "Apps"
3. At the top right, click on "Discover Apps"
4. At the top right, click on "Custom App"
5. Enter the "Application Name"
   1. I used "docker-makemkv"
6. In "Repository", put "jlesage/makemkv" without quotation marks
   1. From: Unable to deploy in Docker/Truenas #197 (reply in thread)
7. Add my MakeMKV license key:
   1. Click on the "Add" button to the right of "Environment Variables"
   2. Put "MAKEMKV_KEY" in the "Name" field, without quotes
   3. The value is my key (from my password repository)
   4. From: the environmental variables section of: https://github.com/jlesage/docker-makemkv
8. Disable VNC
   1. Click on the "Add" button to the right of "Environment Variables"
   2. Put "VNC_LISTENING_PORT" in the "Name" field
   3. Put "-1" in the "Value" field
9. Make the GUI available over the web interface:
   1. In the "Network" section, enable the "Host Network" option.
   2. Note: The "Web UI" button will not show up in the "Application Info" for the app
   3. Note: By default the Web UI will be on port 5800 (http://<IP address>:5800) unless you change it with the WEB_LISTENING_PORT environmental variable, set in the same way as the MakeMKV License key in the step above.
10. Let the app see the USB drives
    1. In the "Security Context Configuration", enable "Privileged"
    2. Note: It would be more secure to use "Capabilities", but I don't know how to do that yet
    3. From: https://www.reddit.com/r/truenas/comments/1fzi0ue/usb_passthrough_on_a_custom_truenas_app_in/
11. Ensure the app can output where I want it to go:
    1. In the "Storage Configuration" section, click the "Add" button to the right of "Storage".
    2. Change "Type" to "Host Path"
    3. In the "Mount Path" field, enter "/output" without quotes
    4. In the "Host path", select the folder you want the output (I chose: /mnt/main_pool/media/MakeMKV)
    5. From: the "Data Volumes" section of: https://github.com/jlesage/docker-makemkv
12. Click on the "Install" button at the bottom of the page

On my system, both USB blue ray players were visible to the app. So that I could use both USB players at the same time, I created a second app named "docker-makemkv-pioneer" and changed the WEB_LISTENING_PORT to 5810. Then, in each app, I go to the "IO" tab and select "Ask for single drive mode". This makes it easier for me to make sure which disk is in which drive.