Thank you always for your patience.
I’ll preface this by saying that I’m trying to run PLEX with docker to which two nas are to be connected in nfs autofs, here are my configurations :
fstab:
192.168.10.3:/volume1/Video /media/Synology/Film nfs defaults 0 0
192.168.10.4:/volume1/Video /media/Synology/SerieTV nfs defaults 0 0
/etc/auto.master
/- /etc/auto.mount --timeout=10
/etc/auto.mount
/media/Synology/Film -fstype=nfs4,ro 192.168.10.3:/volume1/Video
/media/Synology/SerieTV -fstype=nfs4,ro 192.168.10.4:/volume1/Video
this is what happens if I do an ls from debian and both nas are turned off
cd /media/Synology/
ls
ls: cannot access ‘Film’: No such file or directory
ls: cannot access ‘SerieTV’: No such file or directory
Film SerieTV
if I turn the first nas
ls /media/Synology/
ls: cannot access ‘/media/Synology/SerieTV’: No such file or directory
Film SerieTV
If I try to create the docker while nas is off
sudo docker-compose up -d
[+] Running 5/5
plex 4 layers [⣿⣿⣿⣿] 0B/0B Pulled 4.7s
5544ebdc0c7b Pull complete 1.4s
b36f82e974c3 Pull complete 1.8s
37820355e5b7 Pull complete 1.8s
3d16035a9415 Pull complete 3.2s
[+] Running 0/1
⠿ Container plex Starting 0.9s
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting “/media/Synology/Film” to rootfs at “/media/nvme/OSAPP/Docker/plex/film”: mount /media/Synology/Film:/media/nvme/OSAPP/Docker/plex/film (via /proc/self/fd/6), flags: 0x5000: no such file or directory: unknown
this is my docker-compose configuration file
version: "3.9"
services:
plex:
container_name: plex
image: plexinc/pms-docker
restart: unless-stopped
ports:
- 32400:32400/tcp
- 3005:3005/tcp
- 8324:8324/tcp
- 32469:32469/tcp
- 32410:32410/udp
- 32412:32412/udp
- 32413:32413/udp
- 32414:32414/udp
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Rome
- PLEX_CLAIM=secret
- ADVERTISE_IP=http://192.168.10.100:32400/
volumes:
- ./config:/config
- ./plex:/data
- type: bind
source: /media/Synology/Film
target: /media/nvme/OSAPP/Docker/plex/film/
- type: bind
source: /media/Synology/SerieTV
target: /media/nvme/OSAPP/Docker/plex/serietv/
If I run compose with only the first nas on
sudo docker-compose up -d
[+] Running 5/5
plex 4 layers [⣿⣿⣿⣿] 0B/0B Pulled 5.1s
5544ebdc0c7b Pull complete 1.5s
b36f82e974c3 Pull complete 1.9s
37820355e5b7 Pull complete 2.0s
3d16035a9415 Pull complete 3.6s
[+] Running 1/2
Network plex_default Created 0.0s
⠿ Container plex Starting 0.9s
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting “/media/Synology/SerieTV” to rootfs at “/media/nvme/OSAPP/Docker/plex/serietv”: mount /media/Synology/SerieTV:/media/nvme/OSAPP/Docker/plex/serietv (via /proc/self/fd/6), flags: 0x5000: no such file or directory: unknown
If I turn on both nas then it works
sudo docker-compose up -d
[+] Running 1/1
Container plex Started
But beware that usually when I have plex active I use only one nas at a time and if I create the container with both nas turned on and then turn off only one of them it crashes everything.
Whereas if I use Plex “natively” on debian, I don’t experience any problems if I turn off either of the nas.
Maybe this is a limitation of Docker or am I doing something wrong?
thank you very much