Photoprism docker fails to start

  • Hello Folks,


    I've used OpenmediaVault in the past and love the product, but the issue im facing now is driving me bonkers.

    I waned to try out the Photoprism plugin but it keeps failing to start.


    Install went without issue and I was able to define the path etc. However there seems to be an issue with permissions and I dont see anywhere where i can assign photoprism user the necessaryt ACLs. Through ssh i added photoprism user to sudo even and allowed the folders to be accessible to everyone and still get the following:


    What am I doing wrong:


    At the moment Im running openmediavault in a vm for testing:

    Version
    6.0.46-5 (Shaitan)

    Processor

    Kernel
    Linux 5.19.0-0.deb11.2-amd64


    This is the only plugin that is installed and all the latest updates are applied


    Any and all help greatly appreciated

  • ok so i took your hint and reformatted the file system to ext4 and got ahead a bit more:

    Code
    root@openmediavault:~# podman ps --all
    CONTAINER ID  IMAGE                     COMMAND   CREATED        STATUS            PORTS                   NAMES
    2d953fa32075  k8s.gcr.io/pause:3.2                8 minutes ago  Up 8 minutes ago  0.0.0.0:2342->2342/tcp  5b45fc3d6595-infra
    f7278a082081  docker.io/mariadb:latest  mariadbd  8 minutes ago  Up 8 minutes ago  0.0.0.0:2342->2342/tcp  photoprism-db

    However photoprism-app still crashes and i dont see it spin up. Any thoughts?

  • ok quick update... it works now!


    Steps to fix:


    1. Listen to raulfg3

    2. Create an ext4 filesystem

    3. reboot openmediavault

    4. reinstall photoprism

    5. apply changes and reboot

    6. enable photoprism service + apply changes ---> if this still fails check that db and infra is up then reboot openmediavault:

    Code
    dcce5872a37d  k8s.gcr.io/pause:3.2                                          4 minutes ago  Up 4 minutes ago  0.0.0.0:2342->2342/tcp  0bbc3caef4ae-infra
    3673a85fe0d3  docker.io/mariadb:latest                mariadbd              4 minutes ago  Up 4 minutes ago  0.0.0.0:2342->2342/tcp  photoprism-db

    7. After reboot everything should work

  • Hi all,

    I don't want to spam with new topic. I have similiar problem. When I try to open photoprism page, I'm getting HTTP ERROR 502.

    Photoprism is running under OMV 6.0.46-5 (Shaitan) in ESXi virtual enviroment. File Browser plugin works correctly. What I found out is:

    Code
    CONTAINER ID  IMAGE                                     COMMAND               CREATED       STATUS           PORTS                   NAMES
    575937c358af  k8s.gcr.io/pause:3.2                                            41 hours ago  Up 41 hours ago  0.0.0.0:2342->2342/tcp  6827a070f618-infra
    46b15ed82ed4  k8s.gcr.io/pause:3.2                                            41 hours ago  Up 41 hours ago  0.0.0.0:3670->8443/tcp  f5f7164356e3-infra
    3757bb6f4040  docker.io/filebrowser/filebrowser:latest                        41 hours ago  Up 41 hours ago  0.0.0.0:3670->8443/tcp  filebrowser-app
    6e9b5bb5a467  docker.io/library/caddy:latest            caddy run --confi...  41 hours ago  Up 41 hours ago  0.0.0.0:3670->8443/tcp  filebrowser-proxy
    befc6ec32398  docker.io/library/caddy:latest            caddy run --confi...  41 hours ago  Up 41 hours ago  0.0.0.0:2342->2342/tcp  photoprism-proxy
    77e9bb903128  docker.io/mariadb:latest                  mariadbd              41 hours ago  Up 41 hours ago  0.0.0.0:2342->2342/tcp  photoprism-db

    and



    It looks like problem with access bud under ACL permission in OMV all linked folder are set to read/write access for photoprism user.

    What can be wrong with it? Thanks in advance!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!