CorruptDatabaseException for fresh Docker image

Sonarr version (exact version): 2.0.0.5252
Mono version (if Sonarr is not running on Windows):
OS: OSX 10.14.2
Debug logs: https://pastebin.com/aH8UhM9r
Description of issue: After creating a fresh docker image, Sonarr is unable to start due to a CorruptDatabaseException.

Docker create command:

docker create \
    --name sonarr \
    -p 8989:8989 \
    -e PUID=501 \
    -e PGID=501 \
    -e TZ=America/Los_Angeles \
    -v /Users/raphattack/Dropbox/Server/docker/config:/config \
    -v /Users/raphattack/Downloads/Media/Shows:/tv \
    -v /Users/raphattack/Downloads/Media/Downloads:/downloads \
    linuxserver/sonarr

docker logs sonarr: https://pastebin.com/aH8UhM9r

The config folder being inside of Dropbox must have affected the setup. Moving the config folder to a different location succeeded.

Yes, very likely, it’d only be reliable if it was a one way sync and Dropbox never overwrote something Sonarr modified.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.