Shared Storage (deprecated)
Shared Storage, the SeaweedFS cluster that Zerops mounted into your runtime containers through the Shared storage connections page and the mount: import field, is no longer offered. The service type has been retired (the old shared-storage:ha / shared-storage:single type names still work in imports and create a SeaweedFS service), the mount: field is rejected on import, and the connections page is gone from the GUI.
Every existing Shared Storage service has been converted in place into a SeaweedFS service. Same containers, same data, same hostname, no action was needed on your side. The mounts your runtime services had keep working for now through the zeropsSharedStorageMounts environment variable, on a best-effort basis and with a deprecation warning in the runtime log. Take over the mount in your own zerops.yaml with the migration guide before the managed mounts are removed.
For new projects, pick by workload:
- Files shared between containers and services over the network - SeaweedFS. The same managed cluster as before, you mount it or use its filer API yourself.
- A real filesystem with correct locking, for SQLite and other filesystem-based databases or single-node stateful apps - Local Storage.
- Uploads, media, backups - Object Storage.
See Storage on Zerops for the full comparison.
Take over the mount in your zerops.yaml, no data moves.
Copy the data to a Local Storage volume.
Compare the storage services and pick the right one.