Self-host Nextcloud with Levelrail
VerifiedSelf-hosted file sync, sharing, and collaboration, a full private alternative to consumer cloud drives.
- Memory1.5 GiB
- Archarm64
- Services1
How to self-host Nextcloud
-
Pull the images
One image is pulled on your server.
Show images
nextcloud:29.0.4-apache
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
2 secrets are generated and stored encrypted, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Nextcloud requirements
- Memory
- About 1.5 GiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Verified. Verified on arm64 with image tag 29.0.4-apache. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Nextcloud. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Nextcloud docs page.
Deploy Nextcloud your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Nextcloud from the CLI
levelrail-cli templates deploy nextcloud --name my-nextcloud Deploy Nextcloud with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/nextcloud/deploy Nextcloud configuration
Nextcloud services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| nextcloud | nextcloud:29.0.4-apache | 80 | nextcloud_data -> /var/www/html |
Nextcloud environment variables
| Variable | Service | Value |
|---|---|---|
| NEXTCLOUD_ADMIN_PASSWORD | nextcloud | Generated at deploy |
| NEXTCLOUD_ADMIN_USER | nextcloud | Generated at deploy |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: nextcloud_data -> /var/www/html
Nextcloud FAQ
How much memory does Nextcloud need?
The catalog lists about 1.5 GiB of memory for Nextcloud.
Does Nextcloud run on arm64?
For Nextcloud, arm64 is tested; amd64 is image published.
Does Nextcloud need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Nextcloud use?
Nextcloud listens on port 80 inside the stack.
Where does Nextcloud keep its data?
In a named volume: nextcloud_data mounted at /var/www/html.
Can I deploy Nextcloud on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Nextcloud, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image nextcloud:29.0.4-apache is what you deploy there.