Skip to content

Running PhotoPrism on a Raspberry Pi

Our stable releases and preview builds are available as multi-arch Docker images for 64-bit AMD, Intel, and ARM processors.1 As a Raspberry Pi owner, you therefore get the exact same functionality and can follow the same installation steps after going through a short list of system requirements and architecture specific notes.


The easiest way to run PhotoPrism on a Raspberry Pi2 is with PhotoPrismPi. Simply flash the image to an SD card, plug it into the Pi and boot it. After a few minutes, our latest release will be ready to use!

System Requirements

Architecture Specific Notes

Modern ARM64-based Devices

Image Name
Stable Release photoprism/photoprism:latest
Development Preview photoprism/photoprism:preview
MariaDB arm64v8/mariadb:11

Running 64-bit Docker images under Raspbian Linux requires a minimum of technical experience to perform the necessary configuration changes. This is because it is a 32-bit operating system with merely a 64-bit kernel to ensure compatibility with legacy software. If you don't need compatibility with 32-bit apps, we recommend choosing a standard 64-bit Linux distribution instead as it will save you time and requires less experience:

Other distributions that target the same use case as Raspbian, such as CoreELEC, will have similar issues and should therefore also be avoided to run modern server applications.

Raspberry Pi OS

To ensure compatibility with 64-bit Docker images, your Raspberry Pi must boot with the arm_64bit=1 flag in its config.txt file. An "exec format" error will occur otherwise.

Try explicitly pulling the ARM64 version if you've booted your device with the arm_64bit=1 flag and you see the "no matching manifest" error on Raspberry Pi OS (Raspbian):

docker pull --platform=arm64 photoprism/photoprism:latest

It may also help to set the DOCKER_DEFAULT_PLATFORM environment variable to linux/arm64.

In case you see Docker errors related to "cgroups", try adding the following parameters to /boot/firmware/cmdline.txt or /boot/cmdline.txt (file location depends on the OS in use):

cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1

Older ARMv7-based Devices

You may use the following 32-bit Docker images to run PhotoPrism and MariaDB on ARMv7-based devices (always use our ARM64 image if possible):

Image Name
Stable Release photoprism/photoprism:armv7
Development Preview photoprism/photoprism:preview-armv7
MariaDB yobasystems/alpine-mariadb:latest

If your device meets the requirements, mostly the same installation instructions as for regular Linux servers apply. However, you should pay close attention to differences in path and environment variable names.

Darktable is not included in the ARMv7 image because it is not 32-bit compatible. Always choose the regular 64-bit version if your device supports it.

Is a Raspberry Pi fast enough?

This mainly depends on your expectations and the number of files you have. Most users report that PhotoPrism runs smoothly on a Raspberry Pi 4 with 4 GB of RAM.

Note, however, that initial indexing usually takes much longer than on a regular desktop computer and that the hardware has limited video transcoding capabilities, so video file format conversion is not well supported and software transcoding is generally slow. We take no responsibility for instability or performance problems if your device does not meet the requirements.

Getting Updates

Open a terminal and change to the folder where your compose.yaml or docker-compose.yml file is located.3 Now run the following commands to download the newest image from Docker Hub and restart your instance in the background:

docker compose pull
docker compose stop
docker compose up -d

Pulling a new version can take several minutes, depending on your internet connection speed.

Advanced users can add this to a Makefile so that they only have to type a single command like make update. See Command-Line Interface to learn more about terminal commands.

Even when you use an image with the :latest tag, Docker does not automatically download new images for you. You can either manually upgrade as shown above, or set up a service like Watchtower to get automatic updates.

Config Examples

We recommend that you compare your own docker-compose.yml with our latest examples from time to time, as they may include new config options or other enhancements relevant to you.

MariaDB Server

Our config examples are generally based on the latest stable release to take advantage of performance enhancements. This does not mean older versions are no longer supported and you have to upgrade immediately.

If MariaDB fails to start after upgrading from an earlier version (or migrating from MySQL), the internal management schema may be outdated. See Troubleshooting MariaDB Problems for instructions on how to fix this.


If your device runs out of memory, the index is frequently locked, or other system resources are running low:

Other issues? Our troubleshooting checklists help you quickly diagnose and solve them.

You are welcome to ask for help in our community chat. Sponsors receive direct technical support via email. Before submitting a support request, try to determine the cause of your problem.

  1. Experienced users can alternatively use the packages at to manually install PhotoPrism on compatible Linux distributions. For more installation methods, see our Getting Started FAQ

  2. Since our current MicroSD image is based on Ubuntu 22.04 LTS, it is not yet compatible with the Raspberry Pi 5, which requires Ubuntu 23.10+. An updated image will be provided as soon as possible. 

  3. The default Docker Compose config filename is docker-compose.yml. For simplicity, it doesn't need to be specified when running docker compose or docker-compose in the same directory. Config files for other apps or instances should be placed in separate folders.