It wouldn’t start up until I unset and set the pool.
The next issue was my docker containers wouldn’t start up due to missing nvidia drivers, so I had to untick then retick “Install NVIDIA drivers” in the app>configuration>settings to force a reinstall.
The only “official” app I have installed and running is dockge, which in turn runs a number of other stacks.
My expected behaviour is that on a system update, the app system starts itself back up on reboot without having to rest the app pool, and if NVIDIA drivers were installed (and are required for my dockge stacks), then that should happen automatically.
I had this issue once after the upgrade from RC1 to RC2. After the first boot the APPS service would not start.’
After a reboot it took the APPS service about 5 minutes to start, but after that it launched quickly after every following reboot.
So this might be happening for you too.
Well, with the 24.10.0.2 update today I got the chance to check behaviour…and same problem - app system wouldn’t restart on reboot (after waiting an hour), then rebooted again, and waited another hour. No apps.
Had to unset and reset the app pool, then Dockge said it had started, but I couldn’t access the web GUI for it. What I then needed to do is ‘manually’ reinstall the NVIDIA drivers by unchecking and rechecking the ‘Install NVIDIA drivers’ tick box. After which. dockge starts up, along with its containers and stacks. Weird.
Edit: it looks as though the NVIDIA drivers need to be reinstalled manually every update. At least I’ve seen someone else with the same issue on the 24.10.0.2 Announcement board.
Interesting, I did not have to do that. I tried to reproduce the issue on my test system but the APPS (service) just works fine there. Seems to be a rare issue that is rather hard to trigger. On my live system everything works fine now too - only had the APPS service fail to launch that one time.
