Rolling back to 25.04.2 everything is normal, any clues?
1 Like
Did they not run or just not show up in the gui?
Did you check the log under /var/log/app_lifecycle.log if anything unusual was logged?
Was there an error messae in the truenas gui?
Other then that it’s hard to tell because my magic crystal ball isn’t back from maintenance…
The apps service failed to start alltogether. It said I had no pool selected, so I re-selected the one I had selected in 25, and it still said apps service failed to start, so I rolled back. Note, I do have adguard running, and it owns port 53 if that matters.
Is your adguard set as dns server on the nas as well or do you use generic ones e.g. 1.1.1.1 or 8.8.8.8 there? If it’s set to the adguad it may fail to initialize because without adguard it doesn’t have a working connection.
It was a good guess, and I had to check, but I’ve started moving things to another adguard instance because running it on truenas is causing all kinds of trouble.
I disabled adguard, and spun up the goldeye boot and here’s what I get. (Same as last time:
Critical
Failed to start docker for Applications: Docker service could not be started
2025-10-14 16:34:17 (America/Chicago)
Dismiss
Go to Applications
I’m getting this error too. Made a Jira ticket awhile back about it. It started during Beta1 for me and is happening in RC1 for me now as well.
Sit tight 
I am getting this error too after upgrading to 25.10.0 Goldeye (non RC).
The Alerts just said “Failed to start docker for Applications: Docker service could not be started”.
I did find a work around solution on reddit.
Go to the Shell and run sudo systemctl restart middlewared.service, it should restart the Applications and services. Though this is only a work around, because if I were to restart the system again, the “Failed to start docker…” error persists.
Side Note: I am curious if it has anything to do with how the applications are using self signed certificates? I have another system with application with no self sign certificates and them see to worked fine? I am noticing a lot of Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout
1 Like
They closed my ticket out on RC1, said it was fixed in 25.10.0. It is not. Resubmitted another ticket for 25.04.2.5 => 25.10.0.
This did not activate the docker system for me…
Did the command do anything? What was the result of the command?
Some say to this day, @mavproductions is still sitting tight.
The UI restarted (along with presumably all of the other services) but Docker/Apps didn’t come up with it.
Getting this too. Have to Unset, then Choose Pool in Applications. Then have to select Start all Selected manually. Never did this is Fangtooth <.
Man.. All you lucky folks and being able to unset your docker pool! I reboot my truenas and even then before it gets a chance to fully initialize, I login quickly, try to unset and it still says it’s in use! Rock in a hard place here!