OpenCloud can run on ZimaOS because it has official Docker and Docker Compose deployment paths. For a quick local test, use the single-container workflow; for family file sync with HTTPS, use the official Compose stack with integrated Traefik or the external-proxy architecture.
The source user struggled for two weeks with AI-generated instructions. The fix is to stop improvising the stack and follow OpenCloud's own current deployment model, especially its persistent config/data paths, initial admin setup, URL, and proxy/TLS requirements.
Start with a Local Test Instance
The current OpenCloud Docker guide documents a simple container on port 9200.
mkdir -p /DATA/AppData/opencloud/config
mkdir -p /DATA/AppData/opencloud/data
docker pull opencloudeu/opencloud-rolling:latest
docker run --rm -it -v /DATA/AppData/opencloud/config:/etc/opencloud -v /DATA/AppData/opencloud/data:/var/lib/opencloud -e IDM_ADMIN_PASSWORD=CHANGE_ME opencloudeu/opencloud-rolling:latest init
Use the Local Test Only for Validation
The upstream example uses insecure/local settings for quick testing. Do not treat that as a production family-cloud deployment exposed to the internet.
Use Docker Compose for Production
The current OpenCloud Docker Compose guide supports two official architectures: integrated Traefik or an external reverse proxy.
Watch Ports 80 and 443 on ZimaOS
The integrated Traefik stack normally wants standard HTTP/HTTPS ports. If ZimaOS or another reverse proxy already owns them, use the external-proxy path or a separate LAN IP/VM rather than moving the ZimaOS management endpoint casually.
Persist Both Config and User Data
Keep /etc/opencloud and /var/lib/opencloud on durable ZimaOS storage. A container image can be recreated; identity and user data cannot.
Use a Stable Image/Branch for Family Data
The quick-start example uses a rolling image. For a long-lived deployment, follow OpenCloud's production guidance and pin an appropriate stable release/branch after validation rather than updating blindly.
Back Up Before Upgrading
Protect both OpenCloud configuration and data, then test login, sharing, sync clients, and restore after upgrades.
OpenCloud vs Nextcloud
If you mainly need lightweight multi-user file sync, OpenCloud can be a good fit. If you need a larger ecosystem of calendar, contacts, office, plugins, and mature integrations, Nextcloud may still be the more feature-rich choice.
The custom Docker guide provides the ZimaOS side of the workflow.
Choose the Public or Private URL Before Production Setup
OpenCloud generates links and authentication redirects based on its configured URL. Decide the final hostname and HTTPS path before inviting family members so you do not have to migrate clients from a temporary localhost-style URL later.
Verify File Sync with a Non-Admin User
Create a normal family account, upload a test folder from one client, sync it to a second device, then delete/restore a test file. This proves the actual multi-user sync workflow rather than only the admin web login.
Back Up Identity and Configuration Alongside Files
User files alone are not the whole service. Preserve OpenCloud configuration and identity data so accounts, shares, and permissions can be recovered together with the stored files.
FAQ
Can OpenCloud run on ZimaOS?
Yes. ZimaOS supports Docker/Compose and OpenCloud officially documents both container deployment methods.
What port does the simple OpenCloud test use?
The official local Docker example uses port 9200.
Should I use the rolling image for production?
Use it for testing only unless OpenCloud's current production guidance explicitly fits your update strategy.
Do I need Traefik?
No. OpenCloud supports either integrated Traefik or deployment behind an external reverse proxy.
