App Store and S3 storage
Run one-click Docker apps such as n8n, Nextcloud or Uptime Kuma behind a domain, deploy ready-made images, and give customers S3-compatible buckets.
Besides PHP websites, ZoPanel runs applications in Docker containers and can host S3-compatible object storage on the same server. Both are optional components. Install only what you use, because every component uses memory.
Install Docker
Docker is needed for the App Store, image-based deployments and S3 storage. Install it in one of these ways:
- App Store → Install Docker, or
- Components → Docker (admin menu), or
--with docker(or--profile full) when you run the installer.
ZoPanel configures Docker so that containers stay isolated from the host and from hosting accounts:
- User namespaces (
userns-remap): container user IDs map to a range that no hosting account uses. - Local ports only: containers publish their ports on 127.0.0.1 only. They cannot bypass the firewall, and visitors reach them through the website's nginx with SSL.
- Containers cannot talk to each other directly (inter-container communication is off).
- Each container runs with
no-new-privileges, a limit of 512 processes and some Linux capabilities removed (NET_RAW,MKNOD,AUDIT_WRITE). - Memory and CPU limits are set for each app (see the table below; 1 CPU each). A customer's container runs inside the customer's own resource group, so the package's limits also apply.
- App data is stored in
/var/lib/zopanel-apps/<instance>/. Only root and the container can read it. Environment variables are passed through a root-only file, not the command line. - Container logs are rotated (3 files of 10 MB).
App Store
For what each app does and when to choose it, see What each app does.
App Store lists one-click applications. Installing one creates a website for the domain you choose, starts the container, and proxies the domain to it. SSL is issued automatically once the domain points to the server.
| App | Category | Memory limit |
|---|---|---|
| n8n | Workflow automation | 1024 MB |
| Uptime Kuma | Uptime monitoring and status pages | 512 MB |
| Nextcloud | File sync and share, calendar, contacts | 1024 MB |
| Gitea | Lightweight Git hosting | 512 MB |
| Vaultwarden | Bitwarden-compatible password manager | 256 MB |
| Metabase | Business intelligence dashboards | 1536 MB |
| Ghost | Blogs and newsletters (SQLite) | 768 MB |
| Memos | Lightweight notes | 256 MB |
| Open WebUI | AI chat for OpenAI-compatible APIs and public API providers | 2048 MB |
| OpenClaw | AI assistant you talk to from chat apps (needs an LLM API key) | 2048 MB |
| Excalidraw | Collaborative whiteboard | 256 MB |
Each app has its own guide (setup, first login, backups, updates): n8n, Uptime Kuma, Nextcloud, Gitea, Vaultwarden, Metabase, Ghost, Memos, Open WebUI, OpenClaw, Excalidraw.
Apps that need an API key ask for it during installation. You pay the model provider directly. Apps whose upstream project stopped getting security fixes are no longer offered, but copies already installed can still be managed, and their Docker tab says the project is discontinued: File Browser (archived upstream) and, since 0.4.25, Flowise (discontinued in August 2026).
Install an app
- Open App Store and choose an app.
- Enter the domain. Administrators also choose the hosting account the app belongs to.
- Click Install. The task log shows the image download and start.
- Point the domain's A record to the server if you have not already. SSL follows automatically.
Manage an installed app on its website's Docker tab. Everyone with access to the website sees its status and output there. Administrators can also restart, stop or start it, and use Update to latest to run the image this ZoPanel version pins for the app's version line; your data is kept, and since 0.4.28 it is backed up first (see Updates and security updates). Update to latest stays within the app's major version. When the App Store moves an app to a new major version (Ghost 6 and Uptime Kuma 2 since 0.4.25), apps installed earlier keep their version, and the Docker tab shows a notice (end of life, or a new version available) with Upgrade to …: the app's data is backed up first, the new version migrates it, and Roll back to … restores that backup on the earlier version. Each app's guide describes what to check before upgrading. The account that owns the app can restart, stop and start it too; updates and upgrades are for administrators: ask your hosting provider. If the app generates a login token, it is shown under Login details.
Updates and security updates
Every App Store image is pinned to an exact build (a digest) tested with the ZoPanel release; a moved tag upstream never changes what runs. A ZoPanel update can move a pin to a newer release of the same version line. Installed apps keep the build they run until an administrator presses Update to latest: ZoPanel never updates an app by itself, because a new release may convert the app's data (database migrations happen inside the app) and the owner may want to pick the moment.
Update to latest asks for confirmation. With Back up the app's data first ticked (the default), the app's data is archived first, as Back up now does; if that fails (for example the disk is full), the app is not touched and the task says why. Untick it only if you have another copy. An app that keeps no data (Excalidraw) and an update to the build already running skip the backup. After a new build starts, ZoPanel watches it for a minute and a half: if it stops or keeps restarting (a crash on start, or on the converted data), the build it ran before is started again with the data of that backup, and the task fails saying so; the app still shows its update as waiting. To undo an update that started fine, Restore the backup on the Backups card.
When the newer pin fixes published vulnerabilities of what an install runs, ZoPanel says so:
- The app's Docker tab shows Security update: with the advisories it fixes and, for administrators, Update to . Customers see the notice too, with a request to ask their provider.
- Administrators get The app of has a security update waiting (or N apps have a security update waiting) under Needs your attention on the dashboard.
GET /api/sites/{id}/dockerreturnssecurity_update(from,to,advisories) for scripts and monitoring.
Apply security updates soon. ZoPanel 0.4.34 brings Gitea 28.3.0 (twenty advisories of 28.2.0, 29 for installs on 28.1.0); 0.4.28 brought Flowise 3.1.3 (27 of the 28 advisories of 3.1.2).
Apps on a version that will never get a fix get a warning instead: their Docker tab lists the known vulnerabilities, and the dashboard shows The app of has known vulnerabilities that will not be fixed. That is the case of a discontinued app (File Browser) and of an end-of-life major version (Ghost 5: 27 published vulnerabilities of 5.130.6 are fixed only in Ghost 6; use Upgrade to Ghost 6).
File Browser (discontinued)
File Browser's repository was archived upstream in July 2026; 2.63.23 is its last release, and the App Store no longer offers it. Installs keep running and can be managed, backed up and uninstalled, but 18 vulnerabilities published for 2.63.23 have no fix and never will (among them GHSA-c4fr-5f24-4wrj, upload clean-up deleting folders outside the user's permissions, GHSA-448h-jr2h-3vhp, memory exhaustion, GHSA-xqp3-jq6g-x3qm, authentication bypass with proxy authentication, and command-execution bypasses GHSA-8c9q-7855-wfxq, GHSA-jvpw-637p-h3pw, GHSA-3q2w-42mv-cph4, GHSA-hc8f-m8g5-8362); the Docker tab lists them all. ZoPanel does not change these installs. What to do:
- Move the files elsewhere and uninstall the app (Uninstall app on the Docker tab). The hosting account's File Manager, SFTP and S3 storage cover most uses.
- Until then, restrict who can reach it: on the website's Tools tab, add a Password-protected directory with the directory
/, so a second password is asked before File Browser's own login. Do not create File Browser users you do not trust, and keep its command execution off.
Backups: App Store app data in /var/lib/zopanel-apps/<instance>/ is not included in ZoPanel's account backups or incremental (restic) snapshots. It has its own Backups card on the Docker tab: Back up now, and for administrators a daily or weekly Schedule, how many copies to Keep, Restore and delete. The app is paused for a few seconds while its data is copied. Archives are kept in /var/backups/zopanel-apps (root only); copy important ones off the server. See App and S3 storage backups.
App limits for customers
Customers can install apps themselves when their package allows it. Set the limit in Packages → Docker apps:
0means no apps.- Any other number is the maximum number of apps the account can run.
- Each app is a website of its own and counts toward the package's Websites.
- Each app's memory limit counts toward the package's RAM (MB), and its processes toward Processes (processes and threads, see the table). The package keeps PHP children + 40 processes for its websites, plus 64 for each Git deploy that runs its own server (Node.js, Python, Docker; not a static or PHP deploy).
- An install that would go over any of these is refused with the reason. The App Store shows each customer what is left and why an app cannot be installed.
- These checks apply to every install, by the customer or by an administrator for it. Only the number of apps is the customer's own limit: an administrator may install more for it.
- The server must have room too: an app's memory must fit in what hosting accounts may use of the server's RAM (the rest is kept for the system and grows with the server), and all apps on the server together may be planned at 150% of it (apps rarely peak together; the accounts' memory cap still holds).
| App | Memory | Processes |
|---|---|---|
| Memos, Excalidraw, File Browser | 256 MB | 32 |
| Ghost | 768 MB | 32 |
| n8n | 1024 MB | 48 |
| Uptime Kuma | 512 MB | 48 |
| Gitea | 512 MB | 96 |
| Vaultwarden | 256 MB | 96 |
| OpenClaw | 2048 MB | 160 |
| Open WebUI | 2048 MB | 176 |
| Nextcloud | 1024 MB | 192 |
| Metabase | 1536 MB | 320 |
Processes are measured at start and under 50 concurrent requests, times 1.5. Each app's container is capped there, so one app cannot take what the account's websites and other apps need. Apps run with one CPU and their math libraries use one thread per CPU, so they behave the same on any server size.
When an account reaches its process or memory limit (an app crashing, PHP refusing requests), the account and its provider are notified, and accounts whose apps need more than their plan are listed on the provider's dashboard. A crashed app shows as down in uptime monitoring.
Customers can only install apps from the catalog. Custom images are for administrators.
Custom Docker images
Administrators can run any public image behind a domain with App Store → Custom Docker image. Enter the image, the container port, an optional data path and memory. Images outside the catalog are disabled until you turn them on, as root, on the server:
zopanel ctl feature enable custom-docker
This switch can only be changed on the server, not from the web panel. A compromised panel session therefore cannot start arbitrary containers.
Image-based deployments
A website's Deploy tab can also run your own code as a container:
- Container (Dockerfile): ZoPanel builds the Dockerfile in your repository.
- Ready-made Docker image: enter a public image such as
nginx:1.27orghcr.io/owner/app:v2. Pin a tag. The port comes from thePORTvariable or the image'sEXPOSE.
Both use the normal deployment pipeline: health check, zero-downtime switch-over and Rollback to the last 5 releases. The container listens on 127.0.0.1 only. Both also need zopanel ctl feature enable custom-docker on the server.
Who may use them. The code in a Dockerfile or image is the customer's choice, so these modes are open only to accounts of a full administrator and to packages with Own Docker apps turned on (Packages, off by default). A reseller can grant it only when its own package has it. Accounts made before 0.4.8 that already deploy a container keep running, but the next deploy needs the package switch.
Isolation. Every container, App Store apps and image builds included, is cut off from the server's internal network: private and shared address ranges, link-local addresses (the cloud metadata service at 169.254.169.254 and fd00:ec2::254) and loopback are refused. Containers cannot open connections to each other either, so one customer's container cannot reach another site's app directly, past nginx, the WAF and the setup lock; this holds whatever icc says in /etc/docker/daemon.json (ZoPanel also sets it to false). On the server itself, containers reach only the ports the internet reaches too (web 80/443, mail 25/465/587 and DNS), not the database, Redis or the panel. If these firewall rules cannot be applied, ZoPanel does not start or build containers. A customer's own container also runs with every Linux capability dropped except a short list, cannot gain privileges, uses Docker's default seccomp and AppArmor profiles and never sees the Docker socket or host folders.
S3 object storage
S3 storage gives customers Amazon S3-compatible buckets on your server, for images, uploads, media and backup targets. It uses the Garage engine in a container. The engine needs Docker.
Set it up (administrator)
- Open S3 storage and click Install, or install S3 object storage in Components. Data is stored in
/var/lib/zopanel-storage. - The S3 API listens on 127.0.0.1 only. To use it from outside the server, point a domain's A record to the server and use Publish on a domain. ZoPanel creates a reverse-proxy website for it with automatic SSL.
- Apps then connect to
https://<that domain>with regionus-east-1. Turn on path-style addressing in the S3 client.
Uninstall removes the container. Your data is kept unless you also tick Also delete all data and buckets.
Once installed, the S3 storage page has a Backups card for all buckets, with Back up now, a schedule and Restore, as for apps. See App and S3 storage backups.
Buckets
Every hosting account can create buckets in S3 storage → New bucket:
- Names are 3–63 lowercase letters, digits and hyphens.
- Each bucket has its own access key that works only for that bucket. The secret is shown once. If it is lost, use Rotate key. The old key stops working at once.
- Each bucket is capped at what the account's package leaves when it is created (never more than the package's disk space; at least 64 MB must be left). Buckets count in the account's disk space; while the account is over it, its buckets take nothing more until space is freed.
- An account can have up to 10 buckets. Administrators are not limited.
- The free plan includes 1 bucket on the server. Pro removes the limit.
In Bucket settings you can set CORS origins for websites that call the bucket directly, and Delete objects after (days) for logs or rotating backups. Unfinished uploads are always cleaned after 7 days. Browse files lets you upload, download and delete files and create Share links that expire.
Public buckets
Tick Public to let anyone read files without a key, for example images on a website. You can turn it on or off later. When storage is published on a domain, public files are served at:
https://<storage domain>/<bucket>/<file>
Private buckets need the key or a share link. Downloads from the panel's file browser are always served as attachments.
The bucket key works with any S3 SDK or plugin, such as WP Offload Media, Laravel's S3 driver or the AWS SDK.