Docker Container available

[cryptochrome]

One of the most requested features was a Docker Container. So I built one, and it's now available.

This is a first release, and it's pretty bare-bones, but functional. It includes:

• The full dovi_convert tool with all dependencies
• Bash Shell with everything you need to run dovi_convert commands
• A Web Terminal if you want to use a browser
• Allows you to set UID and GID to run as a specific user

Two flavors are available:

• "Latest" tag: Current stable release
• "Beta" tag: The new Python rewrite of the tool

Full instructions are in the README.md, and a Docker Compose file you can use is also available in the repository.

I am still planning to add a full Web UI with a file browser and full integration of all dovi_convert functions, but this will take a while.

[Vertigo86u2]

Hello could you help me to install it on docker on a synology NAS?

[cryptochrome]

Hello. Unfortunately, I don't have a Synology NAS, so I don't know how to set up Docker containers there. But I found this guide:

https://kb.synology.com/en-global/DSM/help/Docker/docker_container?version=6

Have you tried that?

All the parameters you need to know about can be found here:
https://docs.doviconvert.com/installation/docker

[Vertigo86u2]

Hello thanks a lot. Is there any chance to manage also mp4 files?

[cryptochrome]

Not right now, and I have not planned anything. MKV is the de facto standard for Blu-ray rips, and MP4 containers have so many restrictions that I am not considering them at the moment.

[AnotherDaftPunk]

Maybe i'm just a little slow or something, but i'm having some issues getting the docker running.

Using docker compose and in dockge on unraid. PUID won't let me set the correct setting. on unraid, it should be PUID=99 and PGID 100. if i set it to 99, when it starts, it complains that PUID is out range for dovi_convert and that the minimum limit is 1000.

also, once started, i can't seem to get scan to work. i set the media path the same as i do in every other docker app i use and no matter which way i try, it says it can't find any mkv in the directory. should running a recursive scan go several folders deep from the main data folder and find plenty of mkv files?

one last thing. git user smidly created a web-gui docker app using dovi_convert. it appears it hasn't been updated since he added it to the unraid app store. i know you keep updating dovi_convert with new features. i'm just wondering how far behind his app really is compared to yours and if there's any glaring issues/reasons i should stop using his and try to get your main docker image working?

[cryptochrome]

Ok, then I know what's going on now. The TTYD/xterm.js (the web based terminal) configuration passes a bunch of different fonts to the browser to pick one that it has available. It's like a chain, that currently looks like this:

fontFamily="JetBrains Mono", "Fira Code", Menlo, Consolas, "DejaVu Sans Mono", monospace

Normally, the browser walks down this chain and picks the first font from the list it has installed. If it has none of them, it hits the last one, monospace - which simply picks your system's default monospace font.

Apparently, this isn't working. The browser only receives the first font from the list, the rest is ignored. And if you don't happen to have that font installed, it will use the weird, streched, double-spaced font you see.

I think there is a known bug with xterm.js about this, but I need to do some research and figure out what kind of workaround I can implement.

Stay tuned.

[cryptochrome]

@AnotherDaftPunk I think the font issue is fixed now, at least on my end. If you pull the latest dev container, you can test it. That version also contains the option to pass the UMASK environment variable (you can set it to whatever you like). Let me know if that fixes the permission issues for you.

Thanks!

[AnotherDaftPunk]

All Fixed, thanks!

[cryptochrome]

Thank you for helping me troubleshoot this, @AnotherDaftPunk. I just pushed the changes to the release train of the container image. You can (and should) pull that one (:latest) to receive future updates. dev is not maintained.

[AnotherDaftPunk]

Will do. Thank you for working on it so quickly.