quarto-dev / quarto-dev/quarto-cli
quarto render on shared file storage fails with locked database
Open
@cderv is already working on this.
Since Jul 16, 2025.
bug
file-systems
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
After updating quarto to 1.7.31, we run in the following problem:
We have a mounted shared file system on which we get the following error when rendering a qmd file.
ERROR: database is locked: Error code 5: The database file is locked
Stack trace:
at async Object.openKv (ext:deno_kv/01_db.ts:10:15)
at async ProjectCacheImpl.init (file:///opt/quarto/bin/quarto.js:51070:22)
at async createProjectCache (file:///opt/quarto/bin/quarto.js:51197:5)
at async projectContext (file:///opt/quarto/bin/quarto.js:82381:32)
at async render (file:///opt/quarto/bin/quarto.js:91820:19)
at async Command.actionHandler (file:///opt/quarto/bin/quarto.js:92001:32)
at async Command.execute (file:///opt/quarto/bin/quarto.js:8253:13)
at async Command.parseCommand (file:///opt/quarto/bin/quarto.js:8143:20)
at async quarto (file:///opt/quarto/bin/quarto.js:128476:9)
at async file:///opt/quarto/bin/quarto.js:128506:9
if the file is stored in the home directory of a user, the error does not appear.
We did not have issues rendering qmd files on the shared file system before the update of quarto.
I have tried to remove the deno cache but the error remains.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.