Community Apps

Browse our large and growing catalog of applications to run in your Unraid server. 

Download the Plugin  |  Become a Community Developer


Community-built

All the applications you love—built and maintained by a community member who understands what you need on Unraid. Love a particular app or plugin? Donate directly to the developer to support their work.

Created by a legend

Andrew (aka Squid) has worked tirelessly to build and enhance the experience of Community Apps for users like you. Listen to his story.

Moderated and Vetted

Moderators ensure that apps listed in the store offer a safe, compatible, and consistent experience. Learn more about our guidelines.


packetstream-psclient's Icon

packetstream-psclient

Network ServicesWeb

Residential Proxies Powered By Peer-To-Peer Bandwidth Sharing.

passthroughvpn's Icon

This container solves the problem of containers with no 'VPN' variant. After setting up this container, route your non-VPN Dockers through this one to protect your IP. Or host, for example a game or webserver by using your VPN Provider's IP, if your VPN Provider supports forwarding. Both WireGuard and OpenVPN are supported. Check out https://github.com/DyonR/docker-passthroughvpn for more information and setup instructions. ANY CONTAINER THAT GETS ROUTED THROUGH THIS CONTAINER WILL (BRIEFLY) USE YOUR REAL IP. THIS IS BECAUSE THE PASSTHROUGHVPN CONTAINER NEEDS TO ESTABLISH A CONNECTION WITH THE VPN FIRST. TILL THE VPN CONNECTION IS ESTABLISHED, IT WILL USE YOUR REAL IP.

phpldapadmin's Icon

A docker image to run phpldapadmin. It provides a user interface to an openldap database. It must be on the same custom network as openldap and must be linked via --link openldap:PHPLDAPADMIN_LDAP_HOSTS e.g. --link openldap:example.org An example config.php can be found here: https://github.com/commandprompt/phpldapadmin/blob/master/config/config.php.example

pia-wireguard

Network Services

A Docker container for using WireGuard with PIA. Can output the wiregard conf file to a directory

pictshare's Icon

pictshare

Network ServicesWeb

Host your own images / gifs / mp4s / text / bins and stay in control. Self-hosted imgur/pastebin-like. See https://github.com/HaschekSolutions/pictshare/blob/master/rtfm/DOCKER.md for extra variables that can be added if required.

pihole's Icon

Pi-Hole - let's block those pesky ads This is a template for the official PiHole Docker Make sure that you use bridge mode and give PiHole it's own IP address. Also, if you set you router to give out the PiHole address to clients, make sure that you fix the unRaid servers dns to point to a real DNS Server. Please check https://hub.docker.com/r/pihole/pihole for additioanl variables that you may need.

Pihole-DoT-DoH's Icon

Pihole-DoT-DoH

Network ServicesOther, Security

Pi-Hole - let's block those pesky ads! Now with DNS-over-HTTPS and DNS-over-TLS! pihole.doh! Don't send your DNS queries in plain text. YOU MUST ASSIGN A STATIC IP TO THE DOCKER FOR PIHOLE TO WORK. You must set both DNS1 and DNS2 variables to 127.1.1.1#5153 (DoH) and/or 127.2.2.2#5253 (DoT). To use just DoH or just DoT, set both DNS1 and DNS2 to the same value. Otherwise, same instructions as official Pi-Hole. NOTE 1: Port 53 can only be used with custom br0/br1 network and a static IP address. NOTE 2: DNS lookup rarely ever works with ports other than 53 i.e. see note above about static IP. NOTE 3: UnRaid network settings DNS server cannot point to a docker IP. NOTE 4: This should be drop-in replacement for the now deprecated FLIPPINTURT Template.

Pihole-DoT-DoH's Icon

Pihole-DoT-DoH

Network ServicesOther, Security

Pi-Hole - let's block those pesky ads! Now with DNS-over-HTTPS and DNS-over-TLS! pihole.doh! Don't send your DNS queries in plain text. YOU MUST ASSIGN A STATIC IP TO THE DOCKER FOR PIHOLE TO WORK. You must set both DNS1 and DNS2 variables to 127.1.1.1#5153 (DoH) and/or 127.2.2.2#5253 (DoT). To use just DoH or just DoT, set both DNS1 and DNS2 to the same value. Otherwise, same instructions as official Pi-Hole. NOTE 1: Port 53 can only be used with custom br0/br1 network and a static IP address. NOTE 2: DNS lookup rarely ever works with ports other than 53 i.e. see note above about static IP. NOTE 3: UnRaid network settings DNS server cannot point to a docker IP.

Pihole-DoT-DoH's Icon

Pihole-DoT-DoH

Network ServicesOther, Security

Pi-Hole - let's block those pesky ads! Now with DNS-over-HTTPS and DNS-over-TLS! pihole.doh! Don't send your DNS queries in plain text. YOU MUST ASSIGN A STATIC IP TO THE DOCKER FOR PIHOLE TO WORK. You must set both DNS1 and DNS2 variables to 127.1.1.1#5153 (DoH) and/or 127.2.2.2#5253 (DoT). To use just DoH or just DoT, set both DNS1 and DNS2 to the same value. Otherwise, same instructions as official Pi-Hole. NOTE 1: Port 53 can only be used with custom br0/br1 network and a static IP address. NOTE 2: DNS lookup rarely ever works with ports other than 53 i.e. see note above about static IP. NOTE 3: UnRaid network settings DNS server cannot point to a docker IP.

Pihole-Sync-Sender's Icon

Pihole-Sync-Sender

Network Services

A Docker Container To Sync Two Piholes. This is the Sender/Master, you will need a receiver/secondary on the host who is running the receiver/secondary Pi-Hole. Note: after starting this container the first time please check the log for the public Key.

pihole-unbound's Icon

pihole-unbound

Network ServicesSecurity

This Docker deployment runs both Pi-Hole and Unbound in a single container. The base image for the container is the official Pi-Hole container, with an extra build step added to install the Unbound resolver directly into to the container based on instructions provided directly by the Pi-Hole team. FYI - This template will install the "one-container" version the developer has built.

pipework:1.1.3's Icon

This is the version 1.1.3 of the pipework docker container, the latest container maybe broken so this might work better. Pipework allows you to have a static or dynamic ip for a docker container. This is the Unraid implementation of the dreamcat4 pipework docker container

Pomerium-Proxy's Icon

Pomerium-Proxy beta

Network Services

Pomerium Nginx Proxy - Secure, identity-aware access from anywhere.

Portainer-Agent's Icon

Portainer consists of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine. Portainer uses the Portainer Agent container to communicate with the Portainer Server instance and provide access to the node's resources.

Portainer-BE's Icon

Portainer Business Edition is a fully featured service delivery platform for containerized applications that can be used to manage single and multi-cluster Docker, Swarm, Kubernetes and ACI environments. It is designed to be as simple to deploy as it is to use. The application allows you to manage all your orchestrator resources (containers, images, volumes, networks and more) through a ‘smart’ GUI and/or an extensive API. Notes: • If you would like to extend the capabilities of Portainer, getting extra features over containers, networks, volumes and images, you will need to install the Portainer Agent separately. Search for 'Portainer-Agent' in the Community Apps. • This container needs a license to operate, for additional information on obtaining a FREE license visit https://www.portainer.io/pricing/take5

PortainerCE's Icon

Portainer is a lightweight management UI which allows you to easily manage your different Docker environments (Docker hosts or Swarm clusters). Portainer is meant to be as simple to deploy as it is to use. It consists of a single container that can run on any Docker engine (can be deployed as Linux container or a Windows native container, supports other platforms too). Portainer allows you to manage all your Docker resources (containers, images, volumes, networks and more) ! It is compatible with the standalone Docker engine and with Docker Swarm mode.

poste's Icon

FREE version of Poste.io, full mail server solution. POP3, SMTP, IMAP, Spamassassin, WebMail, WebAdmin. INITIAL SETUP: 0. Requires registered FQDN to send/receive external email. 1. Following ports are used by container for mail: 25, 110, 143, 443, 465, 587, 993, 995 2. Following ports are used by container for webui: 443, 8280 (These may conflict, check your ports) 3. Make a user share for mail data, default is /mnt/user/poste 4. Some or all mail ports may need to be opened, forwarded, or dmz for mail send/receive to work. Optional arguments -e "HTTPS=OFF" To disable all redirects to encrypted HTTP, its useful when you are using some kind of reverse proxy (place this argument before image name!) NOTE: Marked as BETA, simply because author is not an expert in email exchange servers -- software itself looks pretty good.

Postfix-Relay's Icon

Postfix-Relay

Network ServicesOther, Productivity

This runs Postfix (as a relay) in Docker. Most home ISPs block port 25, so outbound emails must be relayed through an external SMTP server (e.g., Gmail). This container acts as a single collections point for devices needing to send email. ⚠️ Postfix acts as an open relay. As such, this is not meant to be run on the internet, only on a trusted internal network! ⚠️ Requirements You must already have a account on an external SMTP server (e.g., Gmail, AWS SES, etc...). Your external SMTP server must be using encryption (i.e., plaintext is not allowed)

PostgreSQL_Alpine's Icon

|------------------------------------------------- | General Information |------------------------------------------------- PostgreSQL, often simply "Postgres", is an object-relational database management system (ORDBMS) with an emphasis on extensibility and standards-compliance. As a database server, its primary function is to store data, securely and supporting best practices, and retrieve it later, as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). It can handle workloads ranging from small single-machine applications to large Internet-facing applications with many concurrent users. Recent versions also provide replication of the database itself for security and scalability. PostgreSQL implements the majority of the SQL:2011 standard, is ACID-compliant and transactional (including most DDL statements) avoiding locking issues using multiversion concurrency control (MVCC), provides immunity to dirty reads and full serializability; handles complex SQL queries using many indexing methods that are not available in other databases; has updateable views and materialized views, triggers, foreign keys; supports functions and stored procedures, and other expandability, and has a large number of extensions written by third parties. In addition to the possibility of working with the major proprietary and open source databases, PostgreSQL supports migration from them, by its extensive standard SQL support and available migration tools. And if proprietary extensions had been used, by its extensibility that can emulate many through some built-in and third-party open source compatibility extensions, such as for Oracle.

PostgreSQL_Immich's Icon

This container (based on PostgreSQL 16) is specifically configured for seamless integration with the Immich container, which requires PostgreSQL equipped with pgvecto a robust Postgres extension enabling vector similarity search functions. The specific version used is tensorchord/pgvecto-rs:pg16-v0.2.0 Configuration Parameters POSTGRES_PASSWORD - Superuser password. Default postgres Note -- If you change this value, remember to update it in the Immich container configuration as well. POSTGRES_USER - Username for the superuser. Default postgres Note -- Alterations to this setting should also be mirrored in the Immich container. POSTGRES_DB - Default database. Default: postgres Note -- Any change here should be replicated in the Immich container configuration. Storage Data and Configuration Path: /mnt/user/appdata/postgresql_immich This is the directory where Postgres stores its application data and configuration files. Network Port 5433 This port is mapped from the default PostgreSQL port 5432 to avoid conflicts if another PostgreSQL container is using the default port.