Will it run on my machine?
Tick the self-hosted apps you want and pick the machine. This page adds up the RAM and disk figures each app's own documentation publishes, compares them with the machine, and checks that every container image in each app's compose file has a build for its CPU. Where an app publishes no figure, it says so instead of guessing.
Tick at least one app.
Memory
Not included in any total: the operating system, Docker itself and the Caddy proxy container also need memory and disk. None of these is added here, because no figure for them is cited on this page; leave headroom for them.
CPU architecture
Disk
How the answer is worked out
- Only published figures. Each RAM and disk figure is the one the app's own site or repository states, copied with its conditions and the date it was checked. Of the one hundred apps, twenty-seven publish a RAM figure for the whole server (Immich, Jellyfin, Home Assistant, PhotoPrism, Stirling-PDF, Grafana, Ghost, Wiki.js, Pi-hole, Plex Media Server, Gitea, Homarr, code-server, authentik, Reactive Resume, ToolJet, Appsmith, Langfuse, Plausible CE, NocoBase, Linkwarden, Termix, Documenso, Dawarich, LibrePhotos, bitmagnet and AdventureLog), Nextcloud publishes one per PHP process, and seventy-two publish none. Only Jellyfin, Stirling-PDF, Wiki.js, Pi-hole, Homarr, Reactive Resume, ToolJet, Appsmith, Langfuse, Linkwarden, Termix, Documenso, LibrePhotos and bitmagnet publish a disk size.
- No figure is never zero. Vaultwarden, Paperless-ngx, Uptime Kuma, Audiobookshelf, Navidrome, FreshRSS, Forgejo, Mealie, Actual Budget, linkding, Miniflux, Kavita, Syncthing, n8n, Open WebUI, BookStack, Memos, ntfy, Vikunja, Gotify, changedetection.io, Authelia, AdGuard Home, wg-easy, Frigate, Firefly III, Tandoor Recipes, Grocy, Homepage, Kopia, Portainer CE, Node-RED, Mosquitto, Zigbee2MQTT, Umami, Calibre-Web and Dozzle publish no RAM figure, so they are listed as no published figure, not counted. Adding them as 0 would make every set look as if it fits.
- Per-process is not per-server. Nextcloud's 128 MB minimum and 512 MB recommended are per PHP process; the total depends on how many run at once, which depends on users and activity. The page shows those figures next to the total but never adds them to it.
- Three verdicts. Fits comfortably when the recommended figures add up to no more than the machine's RAM; tight when only the minimums fit; does not fit when even the minimums are over. Where an app publishes only one of the two figures, that figure is used for both and the table says so (Home Assistant publishes a 2 GB minimum and no recommended figure).
- What to drop first. When a set does not fit, the apps with figures are ordered by minimum RAM, largest first. Dropping from the top until the rest fits leaves the largest number of apps that still fit on their minimums.
- Architecture, image by image. An app counts as running on a Raspberry Pi 4 or 5 only if every image in its compose file (the app, its database, its cache) publishes a
linux/arm64build; on a Pi 3 or Zero 2 W with the 32-bit OS the check is forlinux/arm/v7, and on a mini PC, laptop or x86 VPS forlinux/amd64. The lists come from each image's manifest list, fetched from its registry when the site was built (the same snapshot the builder and the app pages use); the links go to the registry page that shows the same OS/Arch list. Every image of the one hundred apps has alinux/amd64build, and every one but three has alinux/arm64build too: ToolJet is amd64 only, and its system requirements say arm64 is not supported; Dawarich's database image, postgis/postgis:17-3.5-alpine, is amd64 only, and its compose file names imresamu/postgis:17-3.5-alpine for ARM instead; AdventureLog's, postgis/postgis:16-3.5, is amd64 only too, and its docs recommend imresamu/postgis:16-3.5-alpine on ARM. For the 32-bit Pi it is 37 of 100: Nextcloud (its MariaDB image), Immich, Jellyfin, Home Assistant, Paperless-ngx, Audiobookshelf, Mealie, Actual Budget, Stirling-PDF, PhotoPrism, n8n, Open WebUI, Ghost, BookStack, Wiki.js, wg-easy, Frigate, Firefly III (its app and MariaDB images), Tandoor Recipes, Grocy, Homepage, Node-RED, Umami, Calibre-Web, Gitea, Homarr, code-server, authentik, Karakeep, wallabag (its MariaDB image), IT-Tools, HedgeDoc, Seerr, Reactive Resume, ToolJet, Appsmith, Khoj, QwenPaw, Langfuse, Plausible CE, ArchiveBox, Dashy, NocoBase, Neko, Linkwarden, ConvertX, DocuSeal, BentoPDF, Termix, Documenso, MeTube, TREK, RomM, PLANKA, Dawarich, OmniTools, LibrePhotos, Homebox, Photoview, SparkyFitness, Moodist, OliveTin and AdventureLog have at least one image without a 32-bit Arm build. On a 32-bit Arm CPU Docker also pulls anarm/v6build when there is noarm/v7one, which is how Forgejo and Mosquitto count.
What this cannot tell you
- How much the apps really use. Published figures are the projects' own guidance, not measurements of your library. Immich's docs say it can run in 4 GB only with machine learning (face and smart search) turned off; Jellyfin says 4 GB "may be enough" on a Linux server without a desktop. Those conditions are shown next to the figures.
- The operating system, Docker and Caddy. They need memory and disk too and are not in any total.
- CPU speed. The check covers architecture, not speed. What the apps say about CPUs (Jellyfin's CPU figures assume hardware-accelerated transcoding; Immich's machine learning on x86 needs the x86-64-v2 level) is listed under the architecture table when you pick them.
- Which OS your Pi runs. The Pi 4 and Pi 5 rows assume a 64-bit OS, where Docker pulls the
linux/arm64builds; the Pi 3 and Zero 2 W rows assume the 32-bit Raspberry Pi OS (linux/arm/v7). Rununame -m:aarch64is 64-bit,armv7lis 32-bit. - Tags move. Most images follow
latest,stableor a major tag, so a later release could add or drop a platform. The date each list was read is shown with it.
The machines
- Raspberry Pi 4 Model B: Broadcom BCM2711, quad-core Cortex-A72 (Arm v8) 64-bit at 1.8 GHz; RAM 1, 2, 3, 4 or 8 GB. Source: Raspberry Pi 4 Model B product brief checked 2026-09-23
- Raspberry Pi 5: Broadcom BCM2712, quad-core 64-bit Arm Cortex-A76 at 2.4 GHz; RAM 1, 2, 4, 8 or 16 GB. Source: Raspberry Pi 5 product brief checked 2026-09-23
- Raspberry Pi 3 Model B+ (32-bit OS): Broadcom BCM2837B0, Cortex-A53 64-bit SoC at 1.4 GHz; RAM 1 GB. Checked against
linux/arm/v7images, the ones the 32-bit Raspberry Pi OS pulls. Source: Raspberry Pi 3 Model B+ product brief checked 2026-09-25 - Raspberry Pi Zero 2 W (32-bit OS): Broadcom BCM2710A1, quad-core 64-bit SoC (Arm Cortex-A53 at 1 GHz); RAM 0.5 GB (512 MB). Checked against
linux/arm/v7images. Source: Raspberry Pi Zero 2 W product brief checked 2026-09-25 - Mini PC, old laptop, small VPS: x86-64 (
linux/amd64). These vary too much for one figure, so you type your own RAM and free disk.
The figures behind every answer
Each figure links to the page it comes from. The same data, with each app's compose file, is on the app pages; to run a set together, tick them in the builder.
-
Nextcloud
RAM: minimum 128 MB per PHP process, recommended 512 MB per PHP process. Per PHP process, not per server: Nextcloud says the total varies greatly with the number of users, apps, files and server activity. The built-in updater needs at least 256 MB. checked 2026-09-23
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for db. From each image's registry manifest (registry pages: db, redis, app). checked 2026-09-25 -
Immich
RAM: minimum 6 GB, recommended 8 GB. With 4 GB, Immich can run only with machine learning (face and smart search) disabled. If you set Docker resource limits, the Postgres container needs at least 2 GB of its own. checked 2026-09-23
Disk: no published figure. No size is published. Thumbnails and transcoded video add 10-20% to the size of the library on average; the Postgres files are typically 1-3 GB and should be on local SSD, never a network share. (Immich docs: Requirements) checked 2026-09-23
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for immich-server, immich-machine-learning, database. From each image's registry manifest (registry pages: immich-server, immich-machine-learning, redis, database). checked 2026-09-25 -
Jellyfin
RAM: minimum 4 GB, recommended 8 GB. 8 GB is the recommendation for an average deployment; 4 GB "may be enough" for a Linux server without a desktop. Add more on Windows 11. checked 2026-09-23
Disk: recommended 100 GB SSD, no minimum published. For the OS, Jellyfin's own files and the transcoding cache; the media library is extra and may sit on any storage faster than your media's bitrate, network shares included. checked 2026-09-23
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for jellyfin. From each image's registry manifest (registry pages: jellyfin). checked 2026-09-25 -
Vaultwarden
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: vaultwarden). checked 2026-09-25 -
Home Assistant
RAM: minimum 2 GB, no recommended figure published. Published as the minimum for a Home Assistant OS virtual machine. The Container instructions on the same page, which this compose file follows, give no separate figure. checked 2026-09-23
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for homeassistant. From each image's registry manifest (registry pages: homeassistant). checked 2026-09-25 -
Paperless-ngx
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for webserver. From each image's registry manifest (registry pages: broker, db, webserver). checked 2026-09-25 -
Uptime Kuma
RAM: no published figure.
Disk: no published figure. No size published, but network file systems such as NFS are not supported: map the data folder to a local directory or volume. (Uptime Kuma README (Docker Compose)) checked 2026-09-23
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: uptime-kuma). checked 2026-09-25 -
Audiobookshelf
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for audiobookshelf. From each image's registry manifest (registry pages: audiobookshelf). checked 2026-09-25 -
FreshRSS
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: freshrss). checked 2026-09-25 -
Forgejo
RAM: no published figure. No figure. The project only says Forgejo "requires an order of magnitude less resources than other forges". (forgejo.org front page (Lightweight and performant)) checked 2026-09-23
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes (server as arm/v6). From each image's registry manifest (registry pages: server). checked 2026-09-25 -
Mealie
RAM: no published figure. No minimum is published. The official compose file caps the container at 1000M, and the docs recommend an explicit limit because Python can pre-allocate far more memory than it needs on a machine with a lot of RAM. (Mealie docs: Installation, SQLite (Recommended)) checked 2026-09-23
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for mealie. From each image's registry manifest (registry pages: mealie). checked 2026-09-25 -
Actual Budget
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for actual-server. From each image's registry manifest (registry pages: actual-server). checked 2026-09-25 -
Stirling-PDF
RAM: recommended 4 GB, no minimum published. For a small team of 1-10 users; the same page recommends 8-16 GB for 10-50 users. A 50 MB PDF with complex graphics can take 200-500 MB of memory while it is processed, and OCR and PDF-to-image are the heaviest operations. checked 2026-09-23
Disk: recommended 10 GB free space, no minimum published. For a small team of 1-10 users; 50 GB (SSD recommended) for 10-50 users. checked 2026-09-23
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for stirling-pdf. From each image's registry manifest (registry pages: stirling-pdf). checked 2026-09-25 -
linkding
RAM: no published figure. No figure. The installation page only says the 'plus' image variant, which runs Chromium to save page snapshots, needs more memory; this file uses the plain image. (linkding docs: Installation (Using Docker)) checked 2026-09-23
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: linkding). checked 2026-09-25 -
Miniflux
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: miniflux, db). checked 2026-09-25 -
Grafana
RAM: minimum 512 MB, no recommended figure published. Published as "Minimum recommended memory". Some features might need more, and the figure covers the Grafana server only, not the data sources such as Prometheus or Loki that it reads from. checked 2026-09-23
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: grafana). checked 2026-09-25 -
PhotoPrism
RAM: minimum 3 GB, no recommended figure published. Physical memory, plus at least 4 GB of swap. Beyond the minimum, RAM should match the number of CPU cores. The docs advise against a hard memory limit, because the indexer temporarily needs more for large files, RAW images and panoramas. checked 2026-09-23
Disk: no published figure. No size is published. Indexing large collections benefits greatly from local SSD storage, especially for the database and cache files. (PhotoPrism docs: Getting Started (System Requirements)) checked 2026-09-23
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for photoprism, mariadb. From each image's registry manifest (registry pages: photoprism, mariadb). checked 2026-09-25 -
Kavita
RAM: no published figure. No requirement is published; the wiki says "most modern systems should be fine" and that users have reported running it on as little as 256 MB of RAM and a single-core 1 GHz CPU. (Kavita wiki: Getting Started (System Requirements)) checked 2026-09-23
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: kavita). checked 2026-09-25 -
Syncthing
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: syncthing). checked 2026-09-25 -
n8n
RAM: no published figure. No figure is published. n8n does not limit how much data a node fetches, so memory grows with the workflows: many nodes, big items, the Code node and manual runs (which keep a copy for the editor) all raise it. (n8n docs: Fix memory issues) checked 2026-09-25
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for n8n. From each image's registry manifest (registry pages: n8n). checked 2026-09-25 -
Open WebUI
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for ollama, open-webui. From each image's registry manifest (registry pages: ollama, open-webui). checked 2026-09-25 -
Ghost
RAM: minimum 1 GB, no recommended figure published. From the Ubuntu install guide ('a server with at least 1GB memory'). The Docker guide, which also runs MySQL, gives a 2GB/1CPU DigitalOcean droplet as its example server. checked 2026-09-25
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for ghost, db. From each image's registry manifest (registry pages: ghost, db). checked 2026-09-25 -
BookStack
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for bookstack, mariadb. From each image's registry manifest (registry pages: bookstack, mariadb). checked 2026-09-25 -
Wiki.js
RAM: minimum 1 GB, no recommended figure published. For Linux; Windows and macOS usually need a bit more. The process itself usually sits around 70 MB, with short bursts during page rendering and indexing. checked 2026-09-25
Disk: recommended 1 GB, no minimum published. At least 1 GB dedicated to Wiki.js is recommended; text-only wikis rarely exceed a few megabytes, uploads add their own size. checked 2026-09-25
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for wiki. From each image's registry manifest (registry pages: db, wiki). checked 2026-09-25 -
Memos
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: memos). checked 2026-09-25 -
ntfy
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: ntfy). checked 2026-09-25 -
Vikunja
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: vikunja, db). checked 2026-09-25 -
Gotify
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: gotify). checked 2026-09-25 -
changedetection.io
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: changedetection). checked 2026-09-25 -
Authelia
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: authelia). checked 2026-09-26 -
AdGuard Home
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: adguardhome). checked 2026-09-26 -
wg-easy
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for wg-easy. From each image's registry manifest (registry pages: wg-easy). checked 2026-09-26 -
Frigate
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for frigate. From each image's registry manifest (registry pages: frigate). checked 2026-09-26 -
Firefly III
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for app, db. From each image's registry manifest (registry pages: app, db, cron). checked 2026-09-26 -
Tandoor Recipes
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for web_recipes. From each image's registry manifest (registry pages: db_recipes, web_recipes). checked 2026-09-26 -
Grocy
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for grocy. From each image's registry manifest (registry pages: grocy). checked 2026-09-26 -
Homepage
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for homepage. From each image's registry manifest (registry pages: homepage). checked 2026-09-26 -
Kopia
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: kopia). checked 2026-09-26 -
Portainer CE
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: portainer). checked 2026-09-26 -
Pi-hole
RAM: minimum 512 MB, no recommended figure published. From the Prerequisites page, which is written for the installer on a Linux system; the Docker pages give no separate figure. The page adds that Pi-hole "is very lightweight and does not require much processing power". checked 2026-09-29
Disk: minimum 2 GB free, recommended 4 GB free. From the Prerequisites page (written for the installer on a Linux system). checked 2026-09-29
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: pihole). checked 2026-09-29 -
Plex Media Server
RAM: recommended 4 GB, no minimum published. Plex's requirements page: "4GB of RAM is typically more than sufficient for typical installs", and Linux installs "can often happily run with even less". checked 2026-09-29
Disk: no published figure. No minimum. The Docker README says the /config database is "usually a few GB" but can reach "the 100s of GBs" for large libraries, and that transcoder temp files need "the 10s of GB". Your media is extra. (plexinc/pms-docker README on GitHub (bridge networking, PLEX_CLAIM, ADVERTISE_IP, volumes)) checked 2026-09-29
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: plex). checked 2026-09-29 -
Node-RED
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for node-red. From each image's registry manifest (registry pages: node-red). checked 2026-09-29 -
Mosquitto
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes (mosquitto as arm/v6). From each image's registry manifest (registry pages: mosquitto). checked 2026-09-29 -
Zigbee2MQTT
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: zigbee2mqtt). checked 2026-09-29 -
Umami
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for umami. From each image's registry manifest (registry pages: umami, db). checked 2026-09-29 -
Calibre-Web
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for calibre-web. From each image's registry manifest (registry pages: calibre-web). checked 2026-09-29 -
Gitea
RAM: recommended 1 GB, no minimum published. Gitea's docs: "2 CPU cores and 1GB RAM is typically sufficient for small teams/projects." checked 2026-09-29
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for server. From each image's registry manifest (registry pages: server). checked 2026-09-29 -
Dozzle
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: dozzle). checked 2026-09-29 -
Homarr
RAM: minimum 500 MB, no recommended figure published. Homarr's hardware prerequisites: "At least 500MB RAM". checked 2026-09-29
Disk: minimum 600 MB free, no recommended figure published. "At least 600MB of free disk space for the Docker image. SSD is preferred." checked 2026-09-29
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for homarr. From each image's registry manifest (registry pages: homarr). checked 2026-09-29 -
SearXNG
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: core, valkey). checked 2026-09-30 -
code-server
RAM: minimum 1 GB, no recommended figure published. Published as "At the minimum, we recommend" for the machine code-server runs on. Language servers and builds you run inside it need more. checked 2026-09-30
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for code-server. From each image's registry manifest (registry pages: code-server). checked 2026-09-30 -
PrivateBin
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: privatebin). checked 2026-09-30 -
authentik
RAM: minimum 2 GB, no recommended figure published. Published as "A host with at least 2 CPU cores and 2 GB of RAM" for the Docker Compose install, which runs the server, the worker and PostgreSQL. checked 2026-09-30
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for server, worker. From each image's registry manifest (registry pages: postgresql, server, worker). checked 2026-09-30 -
Radicale
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: radicale). checked 2026-09-30 -
Karakeep
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for web, chrome, meilisearch. From each image's registry manifest (registry pages: web, chrome, meilisearch). checked 2026-09-30 -
wallabag
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for db. From each image's registry manifest (registry pages: wallabag, db, redis). checked 2026-09-30 -
IT-Tools
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for it-tools. From each image's registry manifest (registry pages: it-tools). checked 2026-09-30 -
HedgeDoc
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for app. From each image's registry manifest (registry pages: database, app). checked 2026-09-30 -
Seerr
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for seerr. From each image's registry manifest (registry pages: seerr). checked 2026-09-30 -
SiYuan
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: main). checked 2026-10-01 -
Reactive Resume
RAM: minimum 1 GB, recommended 2 GB. Published as "1 vCPU / 1 GB RAM minimum (2 GB recommended if Postgres runs on the same host)", which it does in this file. checked 2026-10-01
Disk: no published figure. Published as "Enough for Postgres + uploads (start with 10-20 GB and scale as needed)". checked 2026-10-01
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for reactive-resume. From each image's registry manifest (registry pages: postgres, reactive-resume). checked 2026-10-01 -
ToolJet
RAM: minimum 4 GB, no recommended figure published. Published for a VM running ToolJet. The same page asks 8 GB of RAM, 2 vCPUs and 20 GB for a separate PostgreSQL server; here PostgreSQL shares the machine. checked 2026-10-01
Disk: no published figure. Published as "At least 8GiB, but can increase according to your requirements". checked 2026-10-01
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) no image for tooljet; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for tooljet. From each image's registry manifest (registry pages: tooljet, postgres). checked 2026-10-01 -
Appsmith
RAM: minimum 8 GB, no recommended figure published. Published as "Plan for at least 8 GB of RAM on the host for this all-in-one deployment": the container runs MongoDB, Redis and PostgreSQL inside it. checked 2026-10-01
Disk: minimum 2 GB free for backups and updates, no recommended figure published. The backup and update guides ask for at least 2 GB of free storage to run; the data itself grows with your apps. checked 2026-10-01
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for appsmith. From each image's registry manifest (registry pages: appsmith). checked 2026-10-01 -
Trilium Notes
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: trilium). checked 2026-10-01 -
Khoj
RAM: no published figure. The setup page's "Minimum 8 GB RAM" and "Minimum 5 GB of Disk" are for running an offline chat model, which this file does not include: it talks to the model provider you add. (Khoj docs: Setup (Docker, admin credentials, anonymous mode, admin panel, offline chat requirements)) checked 2026-10-01
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for database, sandbox, server. From each image's registry manifest (registry pages: database, sandbox, search, server). checked 2026-10-01 -
Glance
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: glance). checked 2026-10-01 -
QwenPaw
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for qwenpaw. From each image's registry manifest (registry pages: qwenpaw). checked 2026-10-01 -
Langfuse
RAM: no published figure. Published as "We recommend that you use at least 4 cores and 16 GiB of memory" for a VM running this compose file. checked 2026-10-01
Disk: no published figure. Published as "choose a sufficient amount of storage, e.g. 100GiB": traces pile up in ClickHouse. checked 2026-10-01
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for langfuse-worker, langfuse-web, clickhouse, minio. From each image's registry manifest (registry pages: langfuse-worker, langfuse-web, clickhouse, minio, redis, postgres). checked 2026-10-01 -
Plausible CE
RAM: recommended 2 GB, no minimum published. Published as "At least 2 GB of RAM is recommended for running ClickHouse and Plausible without fear of OOMs". checked 2026-10-01
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for plausible_events_db, plausible. From each image's registry manifest (registry pages: plausible_db, plausible_events_db, plausible). checked 2026-10-01 -
ArchiveBox
RAM: no published figure.
Disk: no published figure. No minimum is published, only how the archive grows: "ArchiveBox can use anywhere from ~1gb per 1000 Snapshots, to ~50gb per 1000 Snapshots", mostly depending on whether video and audio are saved (YTDLP_ENABLED, YTDLP_MAX_SIZE). (ArchiveBox README (CPUs amd64 and arm64; ~1 GB to ~50 GB per 1000 snapshots)) checked 2026-10-03
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for archivebox. From each image's registry manifest (registry pages: archivebox). checked 2026-10-03 -
Dashy
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for dashy. From each image's registry manifest (registry pages: dashy). checked 2026-10-03 -
Beszel
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: beszel). checked 2026-10-03 -
NocoBase
RAM: minimum 2 GB, recommended 4 GB. Published for the NocoBase application service alone, "≥ 4 GB" recommended; the docs say the database is not included and should be sized separately. checked 2026-10-03
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for app. From each image's registry manifest (registry pages: app, postgres). checked 2026-10-03 -
listmonk
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: app, db). checked 2026-10-03 -
Neko
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for neko. From each image's registry manifest (registry pages: neko). checked 2026-10-03 -
Linkwarden
RAM: recommended 4 GB, no minimum published. Published as "Memory: 4 GB is a comfortable starting point." The docs' Lighter Setup page covers smaller machines. checked 2026-10-03
Disk: minimum 1.5 GB, no recommended figure published. Published as "about 1.5 GB for the image, plus your data"; every saved page adds its screenshot, PDF and archive. checked 2026-10-03
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for linkwarden, meilisearch. From each image's registry manifest (registry pages: postgres, linkwarden, meilisearch). checked 2026-10-03 -
ConvertX
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for convertx. From each image's registry manifest (registry pages: convertx). checked 2026-10-03 -
DocuSeal
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for app. From each image's registry manifest (registry pages: app). checked 2026-10-03 -
BentoPDF
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for bentopdf. From each image's registry manifest (registry pages: bentopdf). checked 2026-10-03 -
Termix
RAM: minimum 512 MB, recommended 1 GB. From the Benchmarks table (Termix v2.7.0): 512 MB for 1-25 hosts, 1 GB for 26-100 ("Most people have under 100 hosts, so 1 core and 1 GB is plenty"; about 118 MB idle). Add 1 GB for remote desktop, which runs guacd as a second container. checked 2026-10-08
Disk: minimum 1 GB, recommended 2 GB. Published as 1 GB for 1-25 hosts and 2 GB for 26-100. checked 2026-10-08
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for termix, guacd. From each image's registry manifest (registry pages: termix, guacd). checked 2026-10-08 -
Documenso
RAM: minimum 1 GB, recommended 2 GB. Published as 1 GB minimum (testing) and "2+ GB" recommended for production; the Docker Compose page asks for "At least 2GB of available RAM". checked 2026-10-08
Disk: minimum 10 GB, recommended 20 GB. Published as 10 GB minimum and "20+ GB" for production. Here the PDFs are stored in the database (NEXT_PUBLIC_UPLOAD_TRANSPORT defaults to database), so it grows with every document. checked 2026-10-08
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for documenso. From each image's registry manifest (registry pages: database, documenso). checked 2026-10-08 -
MeTube
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for metube. From each image's registry manifest (registry pages: metube). checked 2026-10-08 -
TREK
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for app. From each image's registry manifest (registry pages: app). checked 2026-10-08 -
RomM
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for romm, romm-db. From each image's registry manifest (registry pages: romm, romm-db). checked 2026-10-08 -
PLANKA
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for planka. From each image's registry manifest (registry pages: planka, postgres). checked 2026-10-08 -
Gatus
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: gatus). checked 2026-10-08 -
Homer
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: homer). checked 2026-10-08 -
Owncast
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: owncast). checked 2026-10-08 -
Dawarich
RAM: recommended 2 GB, no minimum published. Published as "2GB of RAM and more is recommended". The compose file also caps the app container at 4G of memory and half a CPU (APP_MEMORY_LIMIT, APP_CPU_LIMIT). checked 2026-10-08
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) no image for dawarich_db; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for dawarich_db. From each image's registry manifest (registry pages: dawarich_redis, dawarich_db, dawarich_app, dawarich_sidekiq). checked 2026-10-08 -
OmniTools
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for omni-tools. From each image's registry manifest (registry pages: omni-tools). checked 2026-10-09 -
LibrePhotos
RAM: recommended 4 GB, no minimum published. Published as "it is recommended to have 4GBs of RAM", for an x86 or ARM64 processor; the docs add that ARM64 "will not be as fast". The env file's workerConcurrency (one scan worker per core by default) is where its CPU and RAM go. checked 2026-10-09
Disk: minimum 10 GB, no recommended figure published. Published as "at least 10 GB of HDD Space for the docker images, thumbnails, database and machine learning models", not counting your photos. checked 2026-10-09
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for proxy, db, frontend, backend. From each image's registry manifest (registry pages: proxy, db, frontend, backend). checked 2026-10-09 -
Homebox
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for homebox. From each image's registry manifest (registry pages: homebox). checked 2026-10-09 -
Photoview
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for photoview-prepare, photoview, mariadb. From each image's registry manifest (registry pages: photoview-prepare, photoview, mariadb). checked 2026-10-09 -
SparkyFitness
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for sparkyfitness-server, sparkyfitness-frontend. From each image's registry manifest (registry pages: sparkyfitness-db, sparkyfitness-server, sparkyfitness-frontend). checked 2026-10-09 -
bitmagnet
RAM: minimum 1.3 GB, no recommended figure published. Published as "a rough guide": around 300 MB for bitmagnet and at least 1 GB for its Postgres database, which "will run fastest when it has plenty of RAM and a fast disk, preferably a SSD". checked 2026-10-09
Disk: recommended 80 GB, no minimum published. Published as roughly 80 GB per 10 million torrents, "several months of crawling", with "no upper limit": the index keeps growing while the crawler runs. checked 2026-10-09
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: bitmagnet, postgres). checked 2026-10-09 -
13ft
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) yes. From each image's registry manifest (registry pages: 13ft). checked 2026-10-09 -
Moodist
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for moodist. From each image's registry manifest (registry pages: moodist). checked 2026-10-09 -
OliveTin
RAM: no published figure.
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) yes; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for olivetin. From each image's registry manifest (registry pages: olivetin). checked 2026-10-09 -
AdventureLog
RAM: recommended 2 GB, no minimum published. Published as "at least 2 GB RAM on first boot", when it imports world geography data, and "about 1 GB is usually enough afterward". checked 2026-10-09
Disk: no published figure.
Image for every container: x86-64 PC or NAS (
amd64) yes; Raspberry Pi 4/5, 64-bit OS (arm64) no image for db; Raspberry Pi 3 or Zero 2 W, 32-bit OS (arm/v7) no image for app, db. From each image's registry manifest (registry pages: app, db). checked 2026-10-09