Fresh docker install not starting

[SuperGripM]

Note: Please always try reproducing the issue on the :edge build. There is a chance that it was already fixed. If it's an UI issue, you can try reporducing it on the demo page.

---

Describe the bug

A freshly pulled install (edge) isn't starting. Used to work on 3.0, but I cleared the directory due to breaking changes. Reports the following:

5/23/2026, 12:47:12 PM[DEBUG][JobManager] skipping schedule:Temp Folder Cleaning pigallery2 | Error: Invalid search query: directory(type: 102) query should contain 'value' property. Query got: {"type":102,"text":"Uncategorised","negate":true,"queryId":"1_1"} pigallery2 | at SearchManager.buildWhereQuery (/app/src/backend/model/database/SearchManager.js:622:19) pigallery2 | at SearchManager.prepareAndBuildWhereQuery (/app/src/backend/model/database/SearchManager.js:335:21) pigallery2 | at async SessionManager.buildContext (/app/src/backend/model/database/SessionManager.js:60:39) pigallery2 | at async ProjectedCacheManager.getAllProjections (/app/src/backend/model/database/ProjectedCacheManager.js:47:25) pigallery2 | at async ProjectedCacheManager.cleanupNonExistingProjections (/app/src/backend/model/database/ProjectedCacheManager.js:66:22) pigallery2 | at async ProjectedCacheManager.init (/app/src/backend/model/database/ProjectedCacheManager.js:28:9) pigallery2 | at async ObjectManagers.initManagers (/app/src/backend/model/ObjectManagers.js:88:17) pigallery2 | at async ObjectManagers.init (/app/src/backend/model/ObjectManagers.js:63:9) pigallery2 | at async Server.init (/app/src/backend/server.js:124:9) Container pigallery2 Stopped

Environment (please complete the following information):

• OS: Ubuntu arm64 24.04 LTS
• Browser [e.g. chrome, safari]

Used app version:

• docker-edge

[bpatrik]

is this after an update? it looks to me that you might be using an old config

[SuperGripM]

Thanks @bpatrik.
It was after an update, but after seeing there were breaking changes I just binned the entire pigallery2 directory, pulled a new config, a new compose (pigallery2-only, as I already have an existing reverse proxy on the host), changed the port mapping and started afresh. That is what is reported before a restart, upon docker compose up

I have tried disabling Search and Indexing on the config file but it changes nothing.

Edit. FWIW, I've attached the config file.

config.json

E2: I've tried rolling back to 3.1, it works perfectly fine after binning the config and recreating. Haven't tried upgrading again.