Updating to 25.04 caused Apps to disappear

Starting from 24.04, I upgraded first to 24.10, then to 25.04. At the end of this process, all my apps have disappeared. Poking around in the shell shows the ix-applications folders are still there. The “pool for apps” setting had defaulted to nothing; I set it back to my pool, to no change. Trying to connect to these apps externally (jellyfin, in this case), doesn’t work, so they aren’t simply running disconnected from the management interface.

I haven’t been able to dredge up anything online about this issue, and I’m wary of digging around too aggressively for fear of breaking something. I have backed up the ix-applications dataset anyway, just in case.

Release notes are important when installing updates…

It looks like you WERE running Dragonfish, which supported APP that run on Kubernetes. That functionality was dropped in Electric Eel. It’s why I didn’t upgrade beyond Dragonfish for over a year.

Last summer there were multiple write ups about it, I’d share them… but the forum says I can’t share URLs. try googling “truenas drops kubernetes” that should get you close. Or “truenas drops kubernetes truecharts”

The good news is that if you configured your apps to use a host path for their configuration data, you can simply point the new docker containers to the path with the configuration data and it should work. At least it did for my StorJ and Unifi apps. I migrated my other "Aar-server apps off to some other location before upgrading.

I think this is what you were going to link to?

Yup! that’s the one! thank you!

Here’s the deadline information from the 25.04 release notes: https://www.truenas.com/docs/scale/25.04/gettingstarted/scalereleasenotes/#truenas-apps.

You’ll need to manually redeploy the apps using the new system in 25.04. I think you might be able to mount the directories in your existing ix-applications dataset as host paths when installing the new apps, but I’ve never tried it. 25.04 and later uses a hidden .ix-apps folder for app data instead of ix-applications, but we recommend host paths instead of ix-volumes for persistent storage.

I’d also recommend taking a look at https://apps.truenas.com/getting-started/, so you know what to expect.

Honestly, the fact there was no migration plan from kubernetes to docker compose is absolutely ridiculous. The TrueNAS maintainers should be absolutely ashamed of themselves, it would have taken very little effort.

Apps were able to be migrated before the changes to the App catalog. It was linked above in my post. You were able to migrate Kubernetes to Docker before that deadline.

Providing a deadline for migrating is ridiculous given that the upgrade is a minor version change and shouldn’t contain breaking changes.

This entire situation is just absolutely ridiculous and a completely self-inflicted blow to confidence in TrueNAS

You are confusing an OS upgrade with changes made with the App catalog. The changes to the App catalog required upgrading in a timely manner. Per-app IP addressing required it.

And that timeline was announced way ahead of the change, I believe almost 6 months…