[BUG] Calibre database is always in readonly mode #332
Comments
|
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
|
Yeah, same issue. Thank you for reporting. I have downgraded it so that it keeps working. |
which version you downgraded to? |
0.6.24-Is300 Actually the latest version works for me again. I don't know what happened or what went wrong. It just seems to have fixed itself. |
|
we on the team and a few others were unable to ever reproduce this issue without using unsupported actions, such as writing to the db from both calibre and calibre-web concurrently, or having it on a file-based remote mount. As those are unsupported, we do not factor them in. As such, we will close this as non-reproducible. |
Is there an existing issue for this?
Current Behavior
I try to start calibre web with database inside docker-image but i've got an error
Oops! Database Error: attempt to write a readonly database.After that steps
Expected Behavior
Should work correctly
Steps To Reproduce
Got an error
FileNotFoundError: [Errno 2] No such file or directory: '/books_internal/.calnotes'why!!!
4. Ok. Lets create another folder
Ok. Success for now
6. Go to interface and try to upload file
7. Got an error
Oops! Database Error: attempt to write a readonly database..8. There is an error in log file
Environment
CPU architecture
x86-64
Docker creation
--- services: calibre-web: image: linuxserver/calibre-web:0.6.24 container_name: calibre-web environment: # - PUID=1000 # - PGID=1000 - TZ=Etc/UTC - DOCKER_MODS=linuxserver/mods:universal-calibre - OAUTHLIB_RELAX_TOKEN_SCOPE=1 volumes: - /var/data/calibre/config:/config - /var/data/calibre/books:/books ports: - 48083:8083 restart: always networks: - calibre_network networks: calibre_network: external: trueContainer logs
The text was updated successfully, but these errors were encountered: