Failing Immich Logic Check

[SamCoppen]

I'm setting up mediakit with Docker compose on Unraid. I've had a look through the docs and community posts and can't seem to find guidance on this.

The container comes up but the GUI shows the following error:

The Qdrant log looks happy, the mediakit log not so much:

Apologies I'm a bit of a docker noob. A brief explanation of the startup checks would be helpful to diagnose what's going on, again sorry if that exists and I've missed it.

[RazgrizHsu]

Thank you for the update.
My initial assessment is that Immich changed the table names in their new version,
which is causing an issue with our logic.

Please give me some time to confirm and implement a fix.

[RazgrizHsu]

I've updated to the new version. Although Immich hasn't officially released a new version, their code has indeed changed. So, to be safe, I've added some checks to our system to detect database changes.

You can pull the new version from Docker Compose and continue using the system securely.

[RazgrizHsu]

No, this sounds like a Qdrant problem. After the version update, did you delete and re-import your vector data?

Data can sometimes be inconsistent due to versioning. Try resetting all data (on the fetch page) and then re-importing it; that should fix it.

[SamCoppen]

I wasn't able to import any vector data before the update, but I've reset all data and tried again.

Importing them is fine. When I process the assets on the "Vector" tab it errors at about 4000 assets. If I run it again it will process them all. Unfortunately still get the same error in the "Similar" tab when I try to find similar.

[RazgrizHsu]

Please describe your execution env,
alos, could you check if your qdrant image is using the latest tag?

My env is ubuntu 24.04, it's working fine with 80k vectros

[SamCoppen]

Environment Information

Unraid 7.1.3
Docker version 27.5.1
Mediakit version: 0.1.9
Immich version: v1.135.3

qdrant:
container_name: immich-mediakit-qdrant
image: qdrant/qdrant:latest

[RazgrizHsu]

I haven't used Unraid before, so I'm not entirely sure about the specific situation.
I think this is usually caused by insufficient memory.
Please take a look at this issue; it might be helpful to you.

#17