dkrysak 0 Posted March 19, 2019 Author Posted March 19, 2019 Did you run a library scan? After every attemp manually. Scanned indivisually and "Scan all Libraries".
dkrysak 0 Posted March 21, 2019 Author Posted March 21, 2019 (edited) OK, I got it working (the library, not SMB), but I had to switch from SMB over to NFS. I tested two ways (with NFS). Using the Docker volume method with an NFS driver. docker volume create \ --driver local \ --opt type=nfs \ --opt o=addr=172.30.1.1,rw \ --opt device=:/media \ nfsmediavol sudo docker run \ --name emby-server \ -d \ --volume /home/media/docker/emby:/config \ --volume nfsmediavol:/mnt/media \ --volume /home/media/out:/mnt/out \ --device /dev/dri/renderD128 \ --publish 8096:8096 \ --publish 8920:8920 \ --env UID=112 \ --env GID=119 \ --env GIDLIST=119,44,122,124 \ emby/embyserver:latest Using an NFS mount through `fstab` and then just passing in via `--volume`. sudo docker run \ --name emby-server \ -d \ --volume /home/media/docker/emby:/config \ --volume /NFS/media:/mnt/media \ --volume /home/media/out:/mnt/out \ --device /dev/dri/renderD128 \ --publish 8096:8096 \ --publish 8920:8920 \ --env UID=112 \ --env GID=119 \ --env GIDLIST=119,44,122,124 \ emby/embyserver:latest And `fstab` was: 172.30.1.1:/media /NFS/media nfs rsize=32768,wsize=32768,nofail,timeo=14,intr I also made sure that UIDs were the same on my host system and the NAS device (for the users) I am just writing this out in case of someone else coming across this, (or I forget in the future). Edited March 21, 2019 by dkrysak
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now