Javinizer via Docker on Synology DSM

[MattePainting]

Thanks to everyone working on this!

Does anyone have the Javinizer web GUI running via Docker on a Synology NAS? I'm trying to get a container up and running, but I'm struggling. My knowledge level is low in general, and nonexistent when it comes to Docker.

I'm using the Synology DSM web interface, and I have Docker installed with the the latest Javinizer image downloaded from Docker Hub. My trouble is with what settings I need to adjust before launching the container, and then how to access it once it's launched.

I will need to change the port from 5000 to something else, as 5000 is what's already in use for Synology DSM itself. Am I correct in assuming the container port should be kept as 5000, and the local port adjusted to something not already in use? Or do I have this backwards?

I'm also not entirely sure what I should be using for file/folder mount paths. I created a folder for Javinizer at the following path on my NAS: /volume1/docker/javinizer Would the mount path for that folder be /data? The GitBook guide suggests mounting the settings file as well. Does this file path: /volume1/docker/javinizer/jvSettings.json with this mount path: /home/Javinizer/src/Javinizer/jvSettings.json make sense?

I plan on using a pretty simple path for the input and output once I have the container running: /volume1/JAV

I've attached screenshots of what the Advanced Settings pages look like in Docker when launching a Javinizer container in Synology DSM, if it helps visualize my questions.

I realize these questions are more about Docker more than Javinizer, but I hope the discussion might help others using Synology.

[jvlflame]

I will need to change the port from 5000 to something else, as 5000 is what's already in use for Synology DSM itself. Am I correct in assuming the container port should be kept as 5000, and the local port adjusted to something not already in use? Or do I have this backwards?

This is correct. Your container port will need to remain as 5000 as that is what the PowerShell Universal instance inside the container is exposing. Your local (host) port is what needs to be changed since that is conflicting with an existing exposed Synology port.

I'm also not entirely sure what I should be using for file/folder mount paths. I created a folder for Javinizer at the following path on my NAS: /volume1/docker/javinizer Would the mount path for that folder be /data? The GitBook guide suggests mounting the settings file as well. Does this file path: /volume1/docker/javinizer/jvSettings.json with this mount path: /home/Javinizer/src/Javinizer/jvSettings.json make sense?

Yep, that's correct.
/volume1/docker/javinizer -> /data
/volume1/docker/javinizer/jvSettings.json -> /home/Javinizer/src/Javinizer/jvSettings.json

I plan on using a pretty simple path for the input and output once I have the container running: /volume1/JAV

In that case you can mount it to any desired folder inside the container.

For example:
/volume1/JAV -> /mnt

In this case, to access your /volume1/JAV folder, you would set your location.input setting within Javinizer to use /mnt. My suggesting to create two folders within the /volume1/JAV folder called input and output, and then set your location.output setting to /mnt/output.

[jvlflame]

I actually recall another user had trouble setting up Javinizer using the Synology Docker GUI, and had to eventually run the docker command via the terminal. I believe it may have been an issue with the "Execution Command" not running correctly. I would suggest you delete the existing container and SSH into your Synology or access the terminal and run docker run --name javinizer -p 20000:5000 -d jvlflame/javinizer:latest.

If it still doesn't work, get the logs of the running container with docker logs javinizer and we can troubleshoot from there.

[MattePainting]

Deleting the container and then starting over using the docker command via SSH did the trick, I'm seeing the PowerShell Universal login page at http://<ip address>:20000 now.

Thanks for the help!

[ghost]

I actually recall another user had trouble setting up Javinizer using the Synology Docker GUI, and had to eventually run the docker command via the terminal. I believe it may have been an issue with the "Execution Command" not running correctly. I would suggest you delete the existing container and SSH into your Synology or access the terminal and run docker run --name javinizer -p 20000:5000 -d jvlflame/javinizer:latest.

If it still doesn't work, get the logs of the running container with docker logs javinizer and we can troubleshoot from there.

thanks for the suggestion, i've run it via ssh and now successfully installed javinizer.
for the moment i already try to sort demo folder (around 1-2 title), and after click sort it move and create new folder to output folder with new .nfo files.

the thing is, i already made a bunch of directories with Actress Name (root folder), and Title (subfolder). I just want the Javinizer made the .nfo files in existing folder, or creating .nfo files without moving the movie file itself. i tried to change the configuration on Javinizer settings but no luck (still moved the movie files)

from what i read on guidebook https://docs.jvlflame.net/ , you can change configuration via cli. can you please tell me how to do it on Synology NAS? is it via container page? because i can't type anything here

or run it via javinizer console?

please kindly help, i'm at loss here

[jvlflame]

@lord2bo sort.movetofolder off should do what you're looking for. Not sure why it isn't.. but one more thing you might also try is using the "Update" checkbox on the sort tab. That will create metadata files without moving files.

Also, you don't need to do Javinizer -OpenSettings within the console. That's built into the settings page. Just click on the "JSON" button to edit it directly.

[ghost]

@lord2bo sort.movetofolder off should do what you're looking for. Not sure why it isn't.. but one more thing you might also try is using the "Update" checkbox on the sort tab. That will create metadata files without moving files.

Also, you don't need to do Javinizer -OpenSettings within the console. That's built into the settings page. Just click on the "JSON" button to edit it directly.

thankyou for the prompt response, it works perfectly.
it is nice to see all my collections organized. lol. thanks again

[mitrestreet]

The above has been really helpful, as someone with a Synology NAS wishing to run this application. However, I have hit an impasse at the next step, and would appreciate any help that can be offered.

I have the Docker container running, am able to login to the Powershell Universal configuration pages, but after following the instructions in the GitBook, am unable to start the dashboard. The error I get on the powershell dashboard is "Failed to start dashboard: Request failed with status code 404"

Looking at the container log, this section seems relevant:
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[1]
An unhandled exception has occurred while executing the request.
System.Exception: Failed to start dashboard.
at Universal.Server.Services.DashboardProxy.Start(Dashboard dashboard) in D:\a\universal\universal\src\Universal.Server\Services\DashboardProxy.cs:line 118
at Universal.Server.Services.DashboardManager.Start(Dashboard dashboard) in D:\a\universal\universal\src\Universal.Server\Services\DashboardManager.cs:line 65
at UniversalAutomation.DashboardController.Start(Int64 id) in D:\a\universal\universal\src\Universal.Server\Controllers\DashboardController.cs:line 163
at lambda_method(Closure , Object , Object[] )
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Logged|17_1(ResourceInvoker invoker)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Universal.Server.Middleware.RoutingMiddleware.Invoke(HttpContext httpContext, IPolicyEvaluator policyEvaluator) in D:\a\universal\universal\src\Universal.Server\Middleware\RoutingMiddleware.cs:line 88
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
at AspNetCoreRateLimit.RateLimitMiddleware`1.Invoke(HttpContext context) in D:\a\universal\universal\src\AspNetCoreRateLimit\Middleware\RateLimitMiddleware.cs:line 109
at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)

What have I done wrong?

[ypyoo]

I have same problem...Is there any progress or solution found yet?

[jvlflame]

I have same problem...Is there any progress or solution found yet?

I don't have a SynoIogy, but I haven't been able to reproduce this issue on my Javinizer docker container. Is it just happening randomly for you or do you have a way to consistently reproduce the error?

[ypyoo]

Thank you for kind reply...
It happen consistently in my Synology NAS

I attached my setting

Again I appreciate for your support and great project!

[ghost]

Thank you for kind reply...
It happen consistently in my Synology NAS

I attached my setting

Again I appreciate for your support and great project!

try look into your json settings, make sure it is filled with true or false expression.
go to settings -> json (click json button to edit)
mine came out the same errors like you, turns out there is null expression there.

hope it helps

[ypyoo]

Thank you! I solved problem and enjoying Javnizer!
The problem was setting.jason file I downloaded it and replace.

I think Mac OS is not good for this solution. Windows' chrome browser is showing better performance. Safari shows error sometimes...

Thank you~have great time!

[ukiya21]

Hello. Hoped can help.. Currently I'm using DS918+. Wanted to know how to update to newer version without removing the old version. I tried to type -UpdateModule on the terminal but nothing happened. TQ

[vuongtt92]

Hi all,
I try to install javinizer via Docker on Synology DSM. I run ssh into synology and run this command XXX@DS918:~$ docker run --name javinizer -p 8600:8600 -d javinizer/javinizer:latest
But I've got this error message:

docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=javinizer": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.

Could you please help? I'm not familiar with code and Docker (very entry level) Thank you everyone