--- title: data_without_disk description: Your app keeps data in files, and it has no disk to keep them on. --- # `data_without_disk` **Severity:** warn. The deploy goes on. Your app keeps data in files and has no [disk](../concepts/disks.md), so those files are lost each time it sleeps, restarts or is deployed again. ## What Kaviris saw One or both of: - your app uses SQLite (for example `better-sqlite3`, `sqlite3`, `go-sqlite3`), found in its dependencies; - while Kaviris tried your app out, it wrote files on its own filesystem (say `data/kuma.db`). Temporary files, logs and caches are left out. ## Why it matters An app on Kaviris runs in a fresh copy of its image every time it starts: after it [sleeps](../concepts/sleep-and-wake.md), after a restart, after a deploy. Anything it wrote outside a disk is gone then: a SQLite database, its setup, its users, uploaded files. ## How to fix it Add a disk where the app keeps its files. The refusal's fix carries the exact change, usually: ```sh kaviris contract edit --patch '[{"op":"add","path":"/components/0/disk","value":{"size":"1Gi","path":"/app/data"}}]' kaviris contract approve ``` In the portal, press **Add a disk** under the warning, then approve the change. No rebuild is needed: the app restarts with the disk. Agents: `update_contract` with `fix.patch`, then `approve_contract`. If the app keeps its files elsewhere, change `path` to that directory. When the files are in the app's own code directory (`/app/db.sqlite3`), the fix asks you to move them first: a disk there would hide your code. Most apps have a setting for it (`DATA_DIR`, the database file's path). Disks are backed up nightly while the app is not running. See [Disks](../concepts/disks.md). [All refusal codes](index.md)