Closed pike00 closed 4 years ago
I figured out the issue. I was trying to configure both linuxserver/sonarr and linuxserver/radarr to the same directory on the host machine (/config). This caused a conflict between sonarr and radarr (as i had setup sonarr first, it continued to work). To solve the problem, make the config directories a sub-folder explicitly (I had assumed the radarr image would have made the subfolder /config/radarr, but it instead dumps everything into /config/).
Here's the version that now works:
---
version: "3.7"
services:
sonarr:
image: linuxserver/sonarr
container_name: sonarr
environment:
- PUID=1000
- PGID=1001
- TZ=America/New_York
- UMASK_SET=022 #optional
volumes:
- /config/sonarr:/config
- /home/will/media/tv/:/tv
- /home/will/media/downloads:/downloads
ports:
- 8989:8989
restart: unless-stopped
radarr:
image: linuxserver/radarr
container_name: radarr
environment:
- PUID=1000
- PGID=1001
- TZ=America/New_York
volumes:
- /config/radarr:/config
- /home/will/media/movies:/tv
- /home/will/media/downloads:/downloads
ports:
- 7878:7878
restart: unless-stopped
Environment
OS: Debain 10 buster
CPU architecture: x86_64 How docker service was installed: Using the convenience script (docker) and following the instructions on this page (docker-compose)
I recently created a docker-compose.yaml with the following code:
However, when I run
docker-compose up -d
, the server isn't running.Upon inspection of the logs, I believe there is an SQLite error:
Here is the full output when I run
docker logs radarr
: radarr.log