I was curious I tempted an other upgrade, I was able to login in version says 5.4.7-1 (usul) but the OMV-Extras page does not look it updated properly,it still look like OMV4 with no docker tab?
Beiträge von Nefertiti
-
-
Well I know you all gonna scream at me, but I think I found the problem there is a BUG in portainer or emby image not sure witch one ( pretty sure it is portainer) when you go in network although it said host it was not, so I switched it is on bridge , pushed deploy, stopped the container went back to network moved it back to host and this time it was working.
-
I created a user Emby on OMV that user has read/write access to all the shares including the config then I create that user when configuring the WebUI for Emby.
This is not usually a good idea, I had to redeploy Emby, I copied the contents of the /config folder to another drive then deleted the one in use. When deploying a new container Emby creates a new /config folder, once complete I copied the data back.
Any problems usually arise from using previous /config folders on any docker container install, best practise is as above.
You know what, actually I do have this user created on my OMV 4. So I am gonna do that in a few when I will switch again you are completely right about the config folders I might have lost ton of custom metadata witch I added on my files,I know I have a backup of all my movies photo and personal stuff thru USB-back up but I do not remember if I included my appdata folder in that.
-
Thanks I appreciate.
I went back to OMV4 to check it again working works right away so this is for sure a permission issue in OMV5
-
I don't use Emby, sorry. I believe there are far more Plex users here, myself included.
But if Emby is anything like Plex, the vast majority of problems seen will be related to incorrect permissions/ownership of the media files when compared to the user/group the container runs as.
Can i get a screen shot of you plex container volumes I am gonna try to see if its running for me?
-
That image is from Manage Emby Server and TBH that has scanned all those folders rather quickly, + because that image is showing cover art or an image from the .nfo or scan it's finding something.
Not sure about that since is using my existing emby config where the covers was already scanned before for the same libraries
-
It was working perfect under omv 4, anyway those disks got aquota.group and Aquota.user I got no idea where they come from?
-
I will see what his happening but so far nothing getting populated they all say No n
No items found.
-
linuxserver/emby:latest should but not emby/embyserver
emby/embyserver:latest will pull amd64 then there are
emby/embyserver_arm32v7:latest
emby/embyserver_arm64v8:latest
I noticed it now TKS
-
@ post 45 you can see I corrected but so far volume issue is there
-
Start a new thread and answer the questions that have been asked of you.
and what questions ??
-
What hardware are you trying to run this on?
Your volume settings are wrong see my post above
Rockpro64 arm machine I thought the arm image should be pull automatically as the one on linuxserver anyway I change it to emby/embyserver_arm64v8
-
I can only assume I am being ignored. Is that so?
And you really should start a new thread as the Subject for this one is not proper due to thread drift.
No I do not ignore you LOL, I can start a new thread if you think it is necessary
-
Sorry I do not get as example with this one
/srv/dev-disk-by-label-WD_10TB_2/Media2/Documentary:/mnt/share1
what part goes in container and what part goes in ghost?
-
-
No idea why anyway I recreates with the stack and the other emby from linuxserver so it make sens now when I see the result in the container I was very confused with the colon ":" part although it does not look it is working either nothing is playing
also if add data in front like in the example I cannot find the folders in emby library Just wondering if is not a permission issue?
Codevolumes: - /path/to/library:/config - /path/to/tvshows:/data/tvshows - /path/to/movies:/data/movies
---
version: "2.1"
services:
emby:
image: linuxserver/emby:beta
container_name: emby
environment:
- PUID=997
- PGID=100
- TZ=America/Los_Angeles
- UMASK_SET=022 #optional
volumes:
- /srv/dev-disk-by-label-WD_10TB_1/AppData/Emby:/config
- /srv/dev-disk-by-label-WD_10TB_2/Media2/Documentary:/Documentary
- /srv/dev-disk-by-label-WD_10TB_2/Media2/Foreign_no_French:/Foreign_no_French
- /srv/dev-disk-by-label-WD_10TB_2/Media2/Movies_French:/Movies_French
- /srv/dev-disk-by-label-WD_10TB_2/Media2/Movies_USA:/Movies_USA
- /srv/dev-disk-by-label-WD_10TB_2/Media2/TV:/TV
- /srv/dev-disk-by-label-WD_10TB_2/Media2/FAMILY:/FAMILY
ports:
- 8096:8096
- 8920:8920 #optional
restart: unless-stopped
-
got error in emby container log
Code-1 }">standard_init_linux.go:211: exec user process caused "exec format error" -1 }"> standard_init_linux.go:211: exec user process caused "exec format error"
I looked at
Codedocker run -d \ --volume /path/to/programdata:/config \ # This is mandatory --volume /path/to/share1:/mnt/share1 \ # To mount a first share --volume /path/to/share2:/mnt/share2 \ # To mount a second share
but with
/mnt/share2
/srv/dev-disk-by-label-WD_10TB_2/Media2
/config
/srv/dev-disk-by-label-WD_10TB_1/AppData/Emby
Got the error above
-
Grrrr! I spoke too fast not playing from OMV5
-
I am not lucky, I just tried again lt just failed
What is wrong with the picture bellow?
Edit
I think I fixed by putting emby/embyserver:latest
-
Yes inside media2 I got several folder but with OMV4 I was able to separate all this directory directly inside emby webui library and find the mount point , Do you think that part may change in OMV5 ?