Minimserver 2.1-2.2 docker container failed to start on DSM 7.2

[simoncn]

(14-09-2025 15:33)ilia.smirnov Wrote:  Hi everyone. FYI - have kinda same problem. DSM 7.1.1 but Minimserver 2.2 container won't start without anything in the logs.

This sounds like a problem with your container settings. Please post the information shown by selecting Details from the Container tab in Container Manager.

[ilia.smirnov]

(15-09-2025 12:07)simoncn Wrote:  Please try this and post the debug output as a file attachment.

See attached log on DSM 7.1.1 - if you need only 7.1.2 then sorry.

[ilia.smirnov]

(15-09-2025 12:11)simoncn Wrote:  Please post the information shown by selecting Details from the Container tab in Container Manager.

I don't have Container Manager, using Docker package. And - you mean this (see attach)?

[simoncn]

(15-09-2025 13:21)ilia.smirnov Wrote:  I don't have Container Manager, using Docker package. And - you mean this (see attach)?

This looks OK. What do you see when you click the Volume and Network tabs?

[simoncn]

(14-09-2025 07:13)jjlizz Wrote:  Indeed, I've tried every method I know, yet information can hardly be accessed.

@jjlizz: Please see post #10 and post #16. If you can provide the information described in these posts, this would be very helpful.

[simoncn]

(15-09-2025 12:07)simoncn Wrote:  I will also look into what I can do to improve the diagnostics provided by MinimServer for this situation.

To see a MinimServer debug log when the container fails to start, do the following.

Instead of running the container from Container Manager or the Docker app, run it from an ssh session like this:

Code:

sudo docker run -v /volume1/MinimServer:/MinimServer -v /volume1/Music:/Music --network host --name minimtest --entrypoint "/bin/sh" minimworld/minimserver:latest /opt/minimserver/bin/startd wait --logLevel debug --set .logFile=/MinimServer/container.log

This writes a debug log to the host file /volume1/MinimServer/container.log. You don't need to use the names minimtest and container.log: any other names will work. For this to work, the /MinimServer volume must not be mapped as read-only.

[ilia.smirnov]

(15-09-2025 18:12)simoncn Wrote:  This looks OK. What do you see when you click the Volume and Network tabs?

see attached file

[simoncn]

There is a problem with your Volume settings. The first Volume setting should map the MinimServer shared folder to /MinimServer (read-only), like this:

   

[ilia.smirnov]

(16-09-2025 21:53)simoncn Wrote:  There is a problem with your Volume settings. The first Volume setting should map the MinimServer shared folder to /MinimServer (read-only), like this:

Thank you! So, it is not possible to link to another folder? The thing is, I already have Minimserver installed as an application on my NAS. I would like to try running it in Docker for experimental purposes without affecting the existing instance, which is functioning well.

[simoncn]

(17-09-2025 06:22)ilia.smirnov Wrote:  The thing is, I already have Minimserver installed as an application on my NAS. I would like to try running it in Docker for experimental purposes without affecting the existing instance, which is functioning well.

This is exactly what happens if you use the recommended settings. The container has its own independent instance of MinimServer and you can add any number of additional independent instances in this way.

The container needs read-only access to the shared folder containing the MinimServer host instance data so that it can verify the license for the MinimServer host instance. No other data from the host instance is used by the container. The container creates its own independent instance data directory in /opt/minimserver/data.