OpenCloud

The official OpenCloud server, turned into a genuine one-click app — no console, no chown, no config editing.

What is this?

OpenCloud is a modern, self-hosted file sync and share platform (the actively maintained fork of ownCloud Infinite Scale). The official image is great, but on Unraid it runs as a fixed non-root user with no PUID/PGID support and needs a manual one-time init step, so a fresh install normally fails with "permission denied". This is a thin wrapper image that fixes exactly that: it runs the first-boot init for you, heals the appdata permissions, and drops to your chosen PUID/PGID — so you just fill in the Unraid template and hit Apply. Nothing is forked or modified beyond that; the OpenCloud binary is the official upstream image.

Highlights

• Genuinely one-click — auto-runs opencloud init on first boot, heals root-owned appdata to your PUID/PGID, then starts the server. No console, no chown, no editing opencloud.yaml

• Serves HTTPS itself on port 9200 (self-signed by default) — works with no reverse proxy, or hands TLS to your proxy with one setting

• No database — OpenCloud is not Nextcloud; there is no MySQL/Postgres to set up. State lives in a local metadata tree plus an embedded message bus

• Optional S3 object storage — point it at any S3-compatible bucket (MinIO, AWS, Backblaze B2, Wasabi) to keep file blobs in object storage (the metadata stays local)

• Two channels — a stable :production tag and a fast-moving :rolling tag, switchable from the template

• PUID/PGID like every well-behaved Unraid container (default 99:100)

• Multi-arch — amd64 + arm64

• Images: junkerderprovinz/opencloud:production (Docker Hub) / ghcr.io/junkerderprovinz/opencloud:production

Requirements

• Unraid 6.10+

• Set an Admin Password in the template before the first start (it is applied during init; log in as user admin)

• Use a fresh, empty Data folder. Do not point Data at an old OpenCloud/oCIS data directory — the on-disk layout and the storage backend (local vs S3) are not interchangeable, and there is no in-place migration

• Behind a reverse proxy: set OpenCloud terminates TLS to false and point your proxy at the container over plain HTTP on port 9200, with the Public URL set to your external https URL

• For S3: create the bucket beforehand (the container does not), and keep backing up the local Data volume — it holds the file-tree metadata even when blobs live in S3

Posting a bug report

Please post:

• Unraid version (Settings → System Information)

• Image tag (:production, :rolling, or a pinned version)

• Output of docker logs --tail 200 OpenCloud

• Whether you use S3 or local storage, and whether you run behind a reverse proxy

• Whether you changed the Data/Config mounts, PUID/PGID, or the TLS settings

GitHub issues with the same info are also welcome: github.com/junkerderprovinz/opencloud/issues

Credits

All the real work is OpenCloud (Apache-2.0) by the OpenCloud team — this project only packages their official image for one-click Unraid use, with a static gosu for the privilege drop. If it saves you a console session, you can buy me a coffee.

Independent, community-maintained packaging — not affiliated with OpenCloud. The wrapper is MIT-licensed; you run it, you own your data and the responsibility.