[BUG] Updates don't seem to work as expected when container is restarted

[DonkeeeyKong]

Describe the bug
I am not sure if I understand the behavior and logs correctly. If this is a misunderstanding, I apologize.

I use this container on an openmediavault machine. Openmediavault's docker compose plugin has a builtin update and backup script, that I run daily. It stops the container (docker compose down), makes a backup of all its data and brings the container back up (docker compose down).

Now I noticed, that after every restart the logs read Scheduling updates every 30 days. But I never saw an actual update of the index happen. There is an import date in the logs (after Starting API with the following settings:). And here I am not sure if I understand this correctly. If the import date is the date of the last index update, then there are no scheduled updates happening at all. Until today, that line was Import Date: 2026-02-11…, even though I have UPDATE_INTERVAL set to 30d. I rebuilt the container today with FORCE_UPDATE set to true and after the download of a new index, it's Import Date: 2026-07-25T23:00:21.000+0000.

To Reproduce
Steps to reproduce the behavior:

1. Set the environment variables UPDATE_STRATEGY=PARALLEL and UPDATE_INTERVAL=30d
2. Restart the container frequently.

Expected behavior
The update interval should be scheduled regardless of when the container was started.

photon-docker configuration:

services:
    photon:
        image: rtuszik/photon-docker:latest
        environment:
            - UPDATE_STRATEGY=PARALLEL
            - UPDATE_INTERVAL=30d
            - LOG_LEVEL=INFO # Options: DEBUG, INFO, ERROR
            #- FORCE_UPDATE=true
        volumes:
            - photon_data:/photon/data # SKIP_BACKUP
        restart: unless-stopped
        #ports:
         #   - "2322:2322"
volumes:
    photon_data:

System Info

• Host OS: Openmediavault 8/Debian 13
• Host Type: Bare-metal, LXC