MinimServer not restarting in QNAP container after update
|
27-07-2018, 09:24
Post: #1
|
|||
|
|||
MinimServer not restarting in QNAP container after update
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 |
|||
29-07-2018, 15:04
Post: #2
|
|||
|
|||
RE: MinimServer not restarting in QNAP container after update
Still have this problem? Let us know - at the moment I am afraid of any update.
|
|||
29-07-2018, 17:42
Post: #3
|
|||
|
|||
RE: MinimServer not restarting in QNAP container after update
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+.
|
|||
30-07-2018, 15:06
Post: #4
|
|||
|
|||
RE: MinimServer not restarting in QNAP container after update
Do you know what the failure message I reported means? Should I just recreate the container from scratch and see what happens?
|
|||
30-07-2018, 17:01
(This post was last modified: 30-07-2018 17:01 by simoncn.)
Post: #5
|
|||
|
|||
RE: MinimServer not restarting in QNAP container after update
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. |
|||
30-07-2018, 20:34
Post: #6
|
|||
|
|||
RE: MinimServer not restarting in QNAP container after update
I have deleted the containers for MinimServer and Java. Downloaded the new dockerfile.bin. Recreated the containers and now seems to be running OK.
|
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)