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

[ilia.smirnov]

(17-09-2025 10:06)simoncn Wrote:  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.

Thannk you very much! Everything happened as you described, all wokrs perfectly!

[jjlizz]

Ok, I've made some tests on this issue. In my case, running a container from command line with proper server config is totally fine. The instance works smoothly just like the package centre version. After this, I tried to move to container manager and here comes the issue. In container manager, no matter I build the container by adding it from zero or copying the existing instance built by command line, it immediately stopped. All the attempt trying to build instance in container manager failed. I tried to map the instance data in /opt/minimserver/data to the host, then got the logs saying "Incorrect syntax for property /opt/minimserver/bin/startd".

[simoncn]

Please post the exact command you used when you tried to map the instance data in /opt/minimserver/data to the host. It sounds like there was some problem with the syntax of this command.

[jjlizz]

(20-09-2025 11:53)simoncn Wrote:  Please post the exact command you used when you tried to map the instance data in /opt/minimserver/data to the host. It sounds like there was some problem with the syntax of this command.

I'm using container manager, so it's all done in the gui. /opt/minimserver/data:/volume1/docker/minimserver/data (both RO and RW are tested but no difference). For command line, -v /opt/minimserver/data:/volume1/docker/minimserver/data works fine. I thougt this might be caused by container manager for how it handles the process of running a instance, cuz the instance would fail to start even it is a copy of an already functional command line instance.

[simoncn]

Container Manager only allows you to map host shared folders into a container.

Why are you trying to do this mapping? If you are trying to obtain diagnostic information from a container that failed to start, you should use the approach described in this section.

Coming back to your original issue, are you still finding that running a MinimServer instance on DSM 7.2.2 using Container Manager with the settings described in this section is not working?

[jjlizz]

(20-09-2025 15:24)simoncn Wrote:  Container Manager only allows you to map host shared folders into a container.

Why are you trying to do this mapping? If you are trying to obtain diagnostic information from a container that failed to start, you should use the approach described in this section.

Coming back to your original issue, are you still finding that running a MinimServer instance on DSM 7.2.2 using Container Manager with the settings described in this section is not working?

No luck. I can run a container by command line based one the pervious reply. With proper configuration, it can work perfectly just like the package centre version. Still any attempt to run it with container manager fails, such as manually creating the instance following the guide, or just duplicate the functional instance built by command line in container manager. The duplicated container has exactly the same configuration compared to the original one (at least container manager shows they are identically same), but the original is totally fine and can be controlled in container manager with no issue, while the dupulicated one would still fail to start.

[simoncn]

When the duplicated container fails to start in Container Manager, please copy the contents into a debug container as described in this section, then use the interactive shell in the debug container to look in the /opt/minimserver/data directory folder of the debug container for any log files or crash files that might provide information about why the container failed to start.

[jjlizz]

(20-09-2025 17:42)simoncn Wrote:  When the duplicated container fails to start in Container Manager, please copy the contents into a debug container as described in this section, then use the interactive shell in the debug container to look in the /opt/minimserver/data directory folder of the debug container for any log files or crash files that might provide information about why the container failed to start.

/opt/minimserver/data is completely blank following the guide. Then I extracted the image made from duplicated container to check if there is any file in /opt/minimserver/data of this image. It's confirmed that no file exists in /opt/minimserver/data.

[simoncn]

This means that MinimServer was not started for some reason.

Can you rebuild the MinimServer Docker image with a different entrypoint setting? Instead of this:

/bin/sh /opt/minimserver/bin/startd wait

use this:

/bin/sh -x /opt/minimserver/bin/startd wait

Now run this image using Container Manager on DSM 7.2.2. This should produce debug output from the MinimServer start script in the ssh terminal window displayed in Container Manager. There should be a lot of output, so please attach the output to a post here as a file attachment. I am hoping there will be information in this debug output that explains why MinimServer did not start.

[jjlizz]

(21-09-2025 17:17)simoncn Wrote:  This means that MinimServer was not started for some reason.

Can you rebuild the MinimServer Docker image with a different entrypoint setting? Instead of this:

/bin/sh /opt/minimserver/bin/startd wait

use this:

/bin/sh -x /opt/minimserver/bin/startd wait

Now run this image using Container Manager on DSM 7.2.2. This should produce debug output from the MinimServer start script in the ssh terminal window displayed in Container Manager. There should be a lot of output, so please attach the output to a post here as a file attachment. I am hoping there will be information in this debug output that explains why MinimServer did not start.

This time there are 4 files. 2 are empty files (minimserver.config and minimserver.config.lock), the other 2 have the same content "Incorrect syntax for property -x" (minimlaunch.log and minimserver-out.log). This is all.