.order_random.pg2conf not working in PiGallery2 (Docker on Raspberry Pi) + persistent .symlinks_backup errors

[chillin250]

Description:
We’re running PiGallery2 in Docker on a Raspberry Pi 4 connected to a 43" display (portrait mode). Setup works well with iCloudPD feeding images into a single album, and indexing functions correctly (manually and at startup).

Problem:
Random order does not work.

Environment:

• Hardware: Raspberry Pi 4, 4GB
• OS: Raspberry Pi OS (full)
• PiGallery2: official Docker image (latest)
• Mount: /media/XXXX/42BF-D5741/Pictures → /app/data/images
• Photos downloaded by iCloudPD into: /media/jbecket2/42BF-D5741/Pictures/Shared_to_Frame
• Chromium kiosk launches PiGallery2 on boot with auto-login + slideshow

Steps Taken:

• Verified indexing works and new photos appear correctly.
• Created .order_random.pg2conf in Shared_to_Frame (empty file, as expected).
• Restarted container and re-indexed.
• Deleted /app/data/db/, /app/data/thumbs/, /app/data/cache/*.
• Confirmed album is correct (Shared_to_Frame).

Result:

• Photos still display sequentially (by date/name).
• .order_random.pg2conf has no effect.
• Logs are flooded with ENOENT errors for non-existent .symlinks_backup_* paths, e.g.: [Error: ENOENT: no such file or directory, stat '/app/data/images/.symlinks_backup_20250921_030002/000001__xxxx.JPG']

Expected Behavior:

• Album should randomize photo order whenever .order_random.pg2conf is present.

Questions:

• Is .order_random.pg2conf currently supported in the official Docker build?
• Could these persistent .symlinks_backup errors be preventing PG2 from applying order files?
• Is there another hidden location where PG2 caches folder references that must be cleared beyond /db, /thumbs, and /cache?
• Is there another way to randomize slideshow?

[bpatrik]

We resolved the question in: #1039