sascha
5205fb3216
NFS-Server 192.168.7.106 kann nur NFSv3. Ohne vers= handelt der Client v4 zuerst aus -> "NFS: Version unavailable" -> sonarrCL stirbt mit Exit 128 (restart=always laeuft ins Leere). Frisch nach Reboot ist zudem nur das nfsv3-Kernelmodul geladen. Fix live verifiziert auf chris@10.7.1.100. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
35 lines
583 B
YAML
35 lines
583 B
YAML
networks:
|
|
arr-chris_network:
|
|
name: arr-chris_network
|
|
|
|
services:
|
|
|
|
|
|
|
|
sonarrCL:
|
|
container_name: sonarrCL
|
|
image: ghcr.io/hotio/sonarr:latest
|
|
restart: always
|
|
environment:
|
|
- PUID=1000
|
|
- PGID=1000
|
|
- TZ=Europe/Berlin
|
|
- UMASK=022
|
|
- CONFIG_DIR=/config/sonarrCL
|
|
networks:
|
|
- arr-chris_network
|
|
ports:
|
|
- 8989:8989
|
|
volumes:
|
|
- /app-config/arr/:/config
|
|
- data:/chris
|
|
|
|
|
|
|
|
volumes:
|
|
data:
|
|
driver: local
|
|
driver_opts:
|
|
type: nfs
|
|
o: "addr=192.168.7.106,nolock,soft,rw,vers=3"
|
|
device: ":/chris"
|