Unable to start Containers service after upgrading to 25.10

Apps and Virtualization
1

Hello,

After upgrading to 25.10 all of my previous LXCs (from 25.04) disappeared and the service was not running, with a configuration error. I figured out this was from my Technitium custom app binding to port 53 of all interfaces. I successfully changed the app to specify an interface, but now when I try to start the Containers service I get a new configuration error:
[EFAULT] Missing dependencies: Profile "scriptcli-storage" in project "default"

I have not found any references to this issue and really have no idea how to proceed.

EDIT: Adding more logs. From /var/log/middlewared.log
[2025/11/20 13:26:38] (ERROR) middlewared.job.run():540 - Job <bound method VirtGlobalService.recover of <middlewared.plugins.virt.global.VirtGlobalService object at 0x7f112754f350>> failed: CallError(‘Missing dependencies: Profile “scriptcli-storage” in project “default”’)
[2025/11/20 13:26:38] (ERROR) middlewared.job.run():540 - Job <bound method VirtGlobalService.setup of <middlewared.plugins.virt.global.VirtGlobalService object at 0x7f112754f350>> failed: CallError(‘Missing dependencies: Profile “scriptcli-storage” in project “default”’)
[2025/11/20 13:26:38] (ERROR) middlewared.job.run():540 - Job <bound method VirtGlobalService.do_update of <middlewared.plugins.virt.global.VirtGlobalService object at 0x7f112754f350>> failed: CallError(‘Missing dependencies: Profile “scriptcli-storage” in project “default”’)

2

I believe you filed a bug ticket with us as well NAS-138621. The conclusion we arrived at was that you originally deployed an LXC using a community-provided tool that changed the incus configuration through unsupported methods resulting in the upgrade breaking the instance because it lost referential integrity.

3

so what is the fix?

5

anyone?

6

The only way to reset Incus back to factory defaults I’m aware of is to reinstall.

7

Correct. If referential integrity is broken there is not a clear way to fix it (perhaps one can go through, manually mount each incus dataset that contains database backup yaml files and surgically fix them in a way that incus can pick back up where it was – with relevant items removed).

This is the reason why the webshell and SSH logins have explicit warnings that changes through them are unsupported and will result in undefined behavior and may result in system failure.