+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: MinimServer not restarting in QNAP container after update (/showthread.php?tid=4976)
MinimServer not restarting in QNAP container after update - daedlo - 27-07-2018 09:24
Simon
After updating my QNAP 451+ to QTS 4.3.4.0644 build 20180710 I noticed that the version of MinimServer I run in a container does not restart. When I try to start it and Java they both come up with the message:
Failed to start container
500 Server Error: Internal Server Error ("error creating overlay mount to /share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay/d40a6d4e212e32dd8541036a7f60d3ae1b04d8510d3ba7b5df7772147087e2cb/merged: no such file or directory")
I am running MinimServer 0.8.5.2 update 123.
Any help appreciated
RE: MinimServer not restarting in QNAP container after update - Pajr0 - 29-07-2018 15:04
Still have this problem? Let us know - at the moment I am afraid of any update.
RE: MinimServer not restarting in QNAP container after update - simoncn - 29-07-2018 17:42
I tried this and the MinimServer container was still working after updating to 4.3.4-0644. I was previously running 4.3.4-0486. This is on an HS-251+.
RE: MinimServer not restarting in QNAP container after update - daedlo - 30-07-2018 15:06
Do you know what the failure message I reported means? Should I just recreate the container from scratch and see what happens?
RE: MinimServer not restarting in QNAP container after update - simoncn - 30-07-2018 17:01
I have never seen this message and I don't know what it means. I suggest you delete the container and image and go through all the steps again.
I have just updated Dockerfile.bin to correct a small bug (not related to your problem), so doing this will also get you the bug fix.
RE: MinimServer not restarting in QNAP container after update - daedlo - 30-07-2018 20:34
I have deleted the containers for MinimServer and Java. Downloaded the new dockerfile.bin. Recreated the containers and now seems to be running OK.