After today’s update, the docker application manager stopped working, but the docker itself works without any problems, and of course all the dozens of containers inside. In the RC2 version, this error also occurred once, and there it was enough to do Unset/Set pool and the problem was fixed, unfortunately it doesn’t work here anymore. Is there anything I can check? fix?
I’m seeing a lot of people with this problem, including myself. Something is definitely wrong wit EE. Hoping ix gets their act together and fixes it soon. Not very good for an enterprise OS. I’ve been holding off switching back to unraid, just waiting for something a lot more stable then this.
The problem is not so bad that we can’t live with it 
installing and managing from the terminal or portainer still works great, but it makes it a bit more complicated to keep track of installed apps for updates. In any case, some decent solution would be welcome.
Please post a bug report.
1 Like
Reported to jira.
once again unused / choose pool fixed the problem
Hi, everyone.
I’m facing that very frustrating issue with TrueNAS ElectricEel-24.10.0.2. Every time I try to access the GUI, the application view appears broken, and I get the message:
“Applications are not running.” Additionally, the alert screen displays the following message:
“Critical: Failed to start docker for Applications: Docker service could not be started.”
I’ve tried several solutions, but the problem persists. This issue has never occurred in previous versions of TrueNAS, and I’ve been using the platform for many years.
In the Terminal Shell, when I run the command service docker status, it shows that Docker is running normally. Furthermore, I can access all the applications directly via IP/Port without any issues. However, the user interface keeps displaying that Docker is not running.
I’ve also tried downgrading to TrueNAS ElectricEel-24.10, but the bug persists. Upgrading back to the latest version (24.10.0.2) didn’t resolve the issue either. I’ve done extensive research in forums, but I haven’t found an effective solution so far.
Does anyone have any recommendations I could try?
Thank you in advance for your help!
try as I did before - first unused pool, then the same as before choose pool. I had this a few times, problem reported for repair
3 Likes
Thank you very much!
After performing this procedure, the applications have apparently reappeared in the grid. Interestingly, when I tried doing this via the shell, it wasn’t effective, but performing it through the GUI seems to have made a difference, causing them to return. I hadn’t tried this approach before.
I’m not sure if this is a definitive solution, but I’ll keep monitoring it.
Thank you so much for the help!
In the case of a manager crash again, you can easily supervise your applications, add new ones, remove them, restart them, etc. via the previously installed Portainer, it’s generally worth having it.
Below you have a link to report a bug to JIRA, maybe a comprehensive solution will appear there sooner
1 Like
I just updated to ElectricEel-24.10.1 and Unset /Set application pool trick does not work anymore (it worked on 24.10.0.2).
Tested also booting previous version but it does not work there anymore either.
Good thing is that all applications are working so not a critical bug but i can’t see the apps in GUI and can’t update them via GUI:
1 Like
Cześć słoniu - try restarting the entire computer first and then unuset / choose pool after that
OR
check first sudo systemctl restart docker and then unuset / choose pool
Jira replied that they don’t see any problems and recommend looking for answers on the forum :-)))))
Just out of curiosity - how many containers do you have installed?
From TrueNAS apps i have only 3 apps but one of them is Dockge and inside it i have more configured.
I tested restarting few times and than unset/set but no luck.
Tested systemctl restart docker after that i clicked unset pool and set pool.
This worked
Sad thing is i’ll have to do it after every restart. Dzięki za pomoc
1 Like
I have about 60 containers in total and I had the idea that these problems were caused by their large number, but I have no way to check it.
I am glad that restarting docker helped, prosze bardzo
Does anyone from the community know the commands that can be used to unset/choose pool? Because it seems that the application manager has a problem with the start-up itself, so it would be enough to throw a script into the start-up that would fix it until a real solution is found?
1 Like
I have portainer as an app and dockge to manage docker containers and apps, but the apps can’t start, so I’m a bit screwed
Sadly, when I run systemctl restart docker, it just stops after authing me
About 200, and I need them every day, so I’m f+ckt
I’m having exactly the same issue, after boot apps work, but not showing in app manager. Luckily after systemctl restart docker, auth, unset and reset they all come back up. But this isn’t a solution in the long run, I cant be doing this after every restart. Also, don’t know if its connected but my Homeassistant VM doesn’t start after boot either have to restart that.
1 Like
I submitted a bug last year about this and they basically told me “we don’t care.” I still have the problem on occasion, but not every time I reboot. Mostly after updates. I see this is still an issue. I’d link to the jira, but the system says I can’t include links