TerraMaster Forum

scoobyfizz wrote: ↑18 Mar 2021, 15:36 it does as before 4.2.09 it was ok and was not getting warning messages about over 90% usage..... even if it did exist before it is worse with this version .

there is no 4.2.09 for the F2-210 as we are an ARM based processor so the highest we can go to is 4.2.08 unless i have missed something?

apologies posted in the wrong one..

I've just updated my f2-220 and... my docker container are all deleted too i really don't want to reconfigure all, specially after hours of work! And i use it for work!
Is there a way to restore it? can i downgrade tos to 4.2.08??

Hi,
1. The docker service is not up, so the image is "invisible"
2. You can reinstall the system(4.2.08), but you need to export system user/user group data and some system configurations, please refer to this link to reinstall the TOS system viewtopic.php?f=75&t=423

Just one more unhappy customer regarding yet another faulty update from Terramaster.

After the update all my docker containers are gone; need to rebuild everything - not exactly the expected outcome.

TMS wrote: ↑27 Mar 2021, 22:38 Hi,
1. The docker service is not up, so the image is "invisible"
2. You can reinstall the system(4.2.08), but you need to export system user/user group data and some system configurations, please refer to this link to reinstall the TOS system viewtopic.php?f=75&t=423

What do you means with "The docker service is not up"? My docker service is running and already tried to restart the Nas. Is there a solution whitout downgrade system or reconfigure all container?
I always supported Terramaster, but these things shouldn't happen because is really a big problem. With these problems how can I recomend you?

Is it possible to let our engineer check it remotely?You can send an email to our tech team to confirm it.
viewtopic.php?f=75&t=608

Thanks for your replay TMS, i contacted support but they said they cant't do anything and i shold reconfigure all my docker container and configuration. It's ridiculous! It's not possible to release that buggy update!!! Next update what i will lost?? Maybe it's time to move on to the more stable competitor. It' s not possible to lost data for an update!!

I'm sorry to hear that you have encountered this problem.
Not all Docker images in this update are unavailable after the update.
We have solved some problems in TOS 4.2.11. Some docker images disappear or cannot start after being updated.
Different docker images require different conditions.
We will test whether more images can work normally after updating.

What is the actual problem with docker ?
I run 5 containers using compose so will I be affected ?
Is there a list of affected container names ?