github pictaria-ai/pictaria-server v1.2.2
Pictaria Server v1.2.2

one hour ago

Pictaria Server v1.2.2 fixes repeated startup failures on Unraid when the data folder is on the user share (/mnt/user, the template default).

Fixes

  • Startup on Unraid: Pictaria Server could start once and then refuse later starts with a false "Persistent-state path collision" error. The startup check now compares file identities exactly, including large inode numbers, while still refusing paths that really refer to the same file. See report #83.

Upgrade

Back up Pictaria, then follow the v1.2.2 upgrade guide. Use the tagged Compose file and matching image:

ghcr.io/pictaria-ai/pictaria-server:1.2.2

From v1.2.1, no new persisted-state migration occurs: contract 15, Enrich schema 12 and settings version 7 are unchanged. No new setting or data-folder change is needed. If no other migration occurred, you can stop the server and return to v1.2.1 without restoring data; that release still has the Unraid startup bug. Switching code does not undo changes already made in Immich.

From v1.0.x or v1.1.0, direct upgrade is supported, but the v1.2 data migrations still run. Retain the complete pre-migration snapshot and matching older build for rollback.

After updating, confirm Settings → Server shows v1.2.2, then restart the container and confirm it stays healthy without a path-collision error.

Node requirements, the Pictaria Frame protocol and the Immich 2.0+ compatibility floor are unchanged. No Immich or Pictaria Frame upgrade is required.

Validation

The full suite on Node 22.23.2 as a non-root user completed with 1,166 tests: 1,161 passed, zero failed and five Chrome-only tests skipped. PR CI passed Server tests, Upgrade compatibility, Container build and boot smoke, and DCO sign-off. Publication hygiene and DCO checks passed. Both container platforms built locally, and a native arm64 rehearsal upgraded a fresh volume from the published 1.2.1 image to 1.2.2 and stayed healthy through two restarts as a non-root user. The startup fix received independent review with no findings.

Local storage does not reproduce Unraid's large inode values. Automated tests cover those values; real Unraid update/restart validation remains outstanding.

See the full changelog.

Published image

Source commit: 3628e0ef3169f9e4fbf6a107d0c634bf6eb1246a.

Verified multi-platform image (linux/amd64 and linux/arm64):

ghcr.io/pictaria-ai/pictaria-server@sha256:3f8889da6218ede13d74b330e851ef9ff6a94ee0df9a2b9f4f727bfba5db1e0e

The 1.2.2 and latest tags resolve to this manifest, which contains both platforms. The published native arm64 container reports version 1.2.2 and Node v22.23.2, runs as non-root UID 1000, and stays healthy after a restart. Its source-revision label matches the commit above. The 1.2.1 tag retains its original manifest digest, sha256:ab24656436246500d457c7155c3b1a6b2001b9cfbaa69ef0e3ef79aea83f8729. Publication checks passed.

Don't miss a new pictaria-server release

NewReleases is sending notifications on new releases.