Self-host ownCloud Infinite Scale with Levelrail
File sync and share platform in one binary with spaces, search and a modern web UI. Initializes its own config and a generated admin password on first start.
- Authorowncloud
- LicenceApache-2.0
- Memory512 MiB
- Services1
How to self-host ownCloud Infinite Scale
-
Pull the images
One image is pulled on your server.
Show images
owncloud/ocis:8.2.3
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 9200.
-
Fill in the secrets
1 secret is generated and stored encrypted, 4 settings are preset, 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.
After the first start
- Sign in as admin with the generated password shown in the deployment variables. Set the public URL setting to the address you serve it on before first use.
ownCloud Infinite Scale requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9200
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then ownCloud Infinite Scale. 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 ownCloud Infinite Scale docs page.
Deploy ownCloud Infinite Scale your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy ownCloud Infinite Scale from the CLI
levelrail-cli templates install ocis --name my-ocis Deploy ownCloud Infinite Scale with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/ocis/install \
-d '{
"name": "my-ocis"
}' ownCloud Infinite Scale configuration
ownCloud Infinite Scale services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| ocis | owncloud/ocis:8.2.3 | 9200 | config -> /etc/ocisdata -> /var/lib/ocis |
ownCloud Infinite Scale environment variables
| Variable | Service | Value |
|---|---|---|
| IDM_ADMIN_PASSWORD | ocis | Generated at deploy |
| OCIS_INSECURE | ocis | Preset by the template |
| OCIS_URL | ocis | Preset by the template |
| PROXY_HTTP_ADDR | ocis | Preset by the template |
| PROXY_TLS | ocis | Preset by the template |
Ports and volumes
- Ports
- 9200
- Volumes
- 2 named mounts: config -> /etc/ocis, data -> /var/lib/ocis
ownCloud Infinite Scale FAQ
How much memory does ownCloud Infinite Scale need?
The catalog lists about 512 MiB of memory for ownCloud Infinite Scale.
Does ownCloud Infinite Scale run on arm64?
For ownCloud Infinite Scale, arm64 support is not confirmed; amd64 is unknown.
What licence is ownCloud Infinite Scale under?
ownCloud Infinite Scale is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does ownCloud Infinite Scale need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does ownCloud Infinite Scale use?
ownCloud Infinite Scale listens on port 9200 inside the stack.
Where does ownCloud Infinite Scale keep its data?
In named volumes: config mounted at /etc/ocis and data mounted at /var/lib/ocis.
Can I deploy ownCloud Infinite Scale 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 ownCloud Infinite Scale, 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 owncloud/ocis:8.2.3 is what you deploy there.