Page 1 of 1
Docker Engine disables itself when I log into TOS
Posted: 06 Feb 2025, 22:29
by bbxtudios
I have a NAS F2-423 configured to shut down automatically at night and turn on in the morning. All my Docker services run perfectly after startup without any issues.
However, when I log into TOS 6 (latest update), I notice that my containers stop working. Upon checking, I see that Docker Engine has been disabled, and I have to manually enable it again.
This is not an issue of Docker failing to start with the NAS—Docker is running fine until I log into the TOS panel. Why is this happening? Has anyone else experienced this issue?
Re: Docker Engine disables itself when I log into TOS
Posted: 14 Feb 2025, 18:27
by cjkelly83
Ive seen a similar issue, but not fully figured out the cause.
I first noticed it when i logged into the NAS via TNAS app, it immediatly shutdown docker. Today, i was logged in and all was good. I was setting up user accounts and suddenly noticed docker engine had shut down.
Will monitor to understand better the trigger, but its really not good.
Re: Docker Engine disables itself when I log into TOS
Posted: 20 Feb 2025, 01:43
by bbxtudios
I just tried to log in directly to the TNAS APP on PC, and yes, the same thing happens to me, I log in and Docker Engine is deactivated, it happens both in the TNAS PC APP, and when entering the control panel via the web... how strange, I was reading the log, and just when the user logs in, the Docker Engine service is disconnected, but I don't know why this happens...
Re: Docker Engine disables itself when I log into TOS
Posted: 20 Feb 2025, 11:49
by TMzethar
We have not observed a similar phenomenon for the time being.
It is speculated that it may be related to system resource constraints (e.g., RAM exhaustion).
Does it help if you close individual services or applications or containers?
Re: Docker Engine disables itself when I log into TOS
Posted: 25 Feb 2025, 11:03
by bbxtudios
TMzethar wrote: ↑20 Feb 2025, 11:49
We have not observed a similar phenomenon for the time being.
It is speculated that it may be related to system resource constraints (e.g., RAM exhaustion).
Does it help if you close individual services or applications or containers?
It's not because of ram, I have 20gb of ram, docker works correctly until I log in to the TOS user panel, if I don't access the panel in days, it doesn't stop working, it just stops working as soon as I log in to TOS, then I go to the app store, installed, and I see docker engine disabled, I enable it and that's it, if I log out and log back in it works correctly, because it is always because of the first start, that is, I have a timer to turn it off and on every day, for example it turns off at 2 in the morning and turns on at 10 in the morning, docker works correctly and all the services that I have in it, then I log in to TOS and Docker Engine stops, if I log in again it does not stop anymore, until the next day when it will have turned off and on automatically, then it will happen again
Re: Docker Engine disables itself when I log into TOS
Posted: 25 Feb 2025, 15:42
by TMzethar
Please update TOS and Docker Engine/Manager to the latest version. If the problem still persists, please contact our technical support email or our official customer service, we can arrange a remote checkup for you.
Re: Docker Engine disables itself when I log into TOS [SOLVED]
Posted: 25 Feb 2025, 22:21
by bbxtudios
TMzethar wrote: ↑25 Feb 2025, 15:42
Please update TOS and Docker Engine/Manager to the latest version. If the problem still persists, please contact our technical support email or our official customer service, we can arrange a remote checkup for you.
I updated yesterday to the latest version, and today when I started TOS it seems that Docker Engine does not stop at the moment, maybe it has been fixed in the latest version? I will continue testing, greetings
Re: Docker Engine disables itself when I log into TOS
Posted: 28 Feb 2025, 01:06
by bbxtudios
Update:
I've been testing for 3 days now, and Docker Engine no longer stops when I log in to the TOS panel, all because of the latest update, so I guess it's already fixed.