## The symptom
A Crawlee/Apify crawler works locally on macOS but throws SQLite `disk I/O
error` when creating the RequestQueue inside a container on Google Cloud Run.
Filesystem writes themselves work fine in the container: not a missing volume
or permissions problem. Only the SQLite-backed storage fails, right at
RequestQueue creation time.
## Why
SQLite's WAL (write-ahead logging) mode does not work on Cloud Run's
filesystem. Everything else in the crawler behaves normally, which is why it
looks so confusing.
## The fix
Disable WAL mode with the environment variable before starting the crawler:
```
APIFY_LOCAL_STORAGE_ENABLE_WAL_MODE=false
```
Set it in your Cloud Run service configuration alongside the other Apify env
vars. The reporter confirmed Apify then runs correctly in GCP with
2.0.7-beta.6 (and later stable).
## The general lesson
"Disk I/O error" from SQLite in a container, when plain file writes work fine,
points at the journal mode, not the disk. Cloud Run's filesystem does not
support WAL; disabling it is the fix, not bigger volumes or different
permissions.