January 5, 20251 yr 6 minutes ago, Albin said: It appears I can't start a new topic so I hope this location will suffice @Albin For future information Nobody can create new threads in the Docker Containers subforum because posts asking for support for a container should post in the existing support thread for that container. (you posted in the support thread for a different container.) You can go directly to the correct place to get support for your container by clicking on its icon in your Unraid webUI and selecting Support.
January 12, 20251 yr Has anyone else succeeded activating tailscale with Emby docker running Unraid 7 ? With my other dockers I'm able to get tailscale registration link in container log but Emby log shows nothing related to tailscale. In Docker tab I get a tailscale icon in Emby network configuration row, however it says "Error gathering Tailscale information from container. Please check the logs and refresh the page" Any ideas?
January 12, 20251 yr 18 minutes ago, Ilkka Ruuskanen said: Any ideas? afaik its not compatible @ich777 may an idea ?
January 12, 20251 yr 45 minutes ago, Ilkka Ruuskanen said: Has anyone else succeeded activating tailscale with Emby docker running Unraid 7 ? The official image is not compatible since it doesn't have tools like apt, apk or pacman because it's based on busybox. When you issue: docker container logs EmbyServer1 You can see the error on top: ======================= Executing Unraid Docker Hook for Tailscale Detecting Package Manager... ERROR: Detection from Package Manager failed! ERROR: Unraid Docker Hook script throw an error! Starting container without Tailscale! Starting container... ======================= (you can't see it because there is a lot going on on startup in Emby) What you can do is switch over to the container from Linuxserver.io which is based on Ubuntu or you could also use the sidecar container method.
January 12, 20251 yr Thank you @ich777 I keep using the official container without tailscale then. Not worth for me to switch to other containers.
January 12, 20251 yr 1 minute ago, Ilkka Ruuskanen said: I keep using the official container without tailscale then. Not worth for me to switch to other containers. Or you could use the sidecar container if you really want to use Tailscale. You could also set it up in the way that it shares a network with a container that is compatible with Tailscale, so to speak, let Emby use the network from another container which works with Tailscale.
January 12, 20251 yr 3 minutes ago, ich777 said: You could also set it up in the way that it shares a network with a container that is compatible with Tailscale, so to speak, let Emby use the network from another container which works with Tailscale. Interesting idea. I might try it out or set up a tailscale subnet router.
March 13, 20251 yr In my Unraid system, I am using Unassigned Devices to mount a shared folder from another device on my LAN via SMB. In the Docker container, Emby uses this mounted remote folder as its media library. However, after every system restart, Emby fails to recognize the media library and only works properly after a manual restart of Emby. I initially thought the issue might be due to Emby starting before the mount is completed, so I set a 120-second delay for Emby's startup, but the problem persists. I'm at a loss as to what might be causing this issue and would appreciate any insights.
March 13, 20251 yr 6 minutes ago, jndhui said: I'm at a loss as to what might be causing this issue and would appreciate any insights. assuming you are using the /mnt point in emby, sample like /mnt/remotes/192.... is it settled as "slave" ? if not, you should try that setting. and this is pretty sure not emby related, more docker related how it can handle the mount from UAD remote, you can check after emby start (after reboot) like this docker exec EmbyServer ls -la /mnt/remotes/192....
March 16, 20251 yr On 3/13/2025 at 2:36 PM, alturismo said: assuming you are using the /mnt point in emby, sample like /mnt/remotes/192.... is it settled as "slave" ? if not, you should try that setting. and this is pretty sure not emby related, more docker related how it can handle the mount from UAD remote, you can check after emby start (after reboot) like this docker exec EmbyServer ls -la /mnt/remotes/192.... The issue has been resolved. After setting it to "slave," I restarted Unraid, and Emby started up accordingly. Now it plays normally without needing to restart Emby again. Thank you so much! It seems I still don’t fully understand the meanings of "slave" and "shared"—I’ll have to study them more carefully.
March 20, 20251 yr Hi there, I have a problem with Emby/Unraid on my new hardware. Hope someone can help me out. My new server consists of an Intel Ultra 9 285K, 64GB RAM and an Asus Z890 ProArt mainboard. On Unraid 7.0 there was no support for the iGPU of my 285K. But now I have Unraid 7.1 Beta and that support is there. However, I can not choose hardware en/decoding in the Emby settings. The iGPU is not present there. When I use the EmbyServerBeta image I do see my iGPU in the settings. However, if I then play a 4K movie at 8Mbps, the processor still does all the work and the iGPU remains at 0% usage and 0W consumption. In both Emby images I have tried both the /dev/dri and the --device=/dev/dri:/dev/dri parameters method. Has the same effect. Does anyone have any idea how I can fix this? skynet-diagnostics-20250320-1632.zip Edited March 20, 20251 yr by JohnVIDnr5
March 31, 20251 yr On 3/20/2025 at 4:33 PM, JohnVIDnr5 said: Hi there, I have a problem with Emby/Unraid on my new hardware. Hope someone can help me out. My new server consists of an Intel Ultra 9 285K, 64GB RAM and an Asus Z890 ProArt mainboard. On Unraid 7.0 there was no support for the iGPU of my 285K. But now I have Unraid 7.1 Beta and that support is there. However, I can not choose hardware en/decoding in the Emby settings. The iGPU is not present there. When I use the EmbyServerBeta image I do see my iGPU in the settings. However, if I then play a 4K movie at 8Mbps, the processor still does all the work and the iGPU remains at 0% usage and 0W consumption. In both Emby images I have tried both the /dev/dri and the --device=/dev/dri:/dev/dri parameters method. Has the same effect. Does anyone have any idea how I can fix this? skynet-diagnostics-20250320-1632.zip 290.32 kB · 0 downloads Does nobody really have a clue after 11 days?
March 31, 20251 yr 36 minutes ago, JohnVIDnr5 said: Does nobody really have a clue after 11 days? i would rather suggest to ask in Emby Forums, the Team there is very helpful
April 27, 20251 yr anyone is able to make the Intel ARC B580 works in the docker? I tried everything, i can't get it to work (i'm on 7.1 RC3)
April 29, 20251 yr On 4/27/2025 at 1:15 PM, Benjamin Picard said: anyone is able to make the Intel ARC B580 works in the docker? I tried everything, i can't get it to work (i'm on 7.1 RC3) If you want help you gotta be specific on what exactly you tried to do.
April 29, 20251 yr 5 hours ago, MowMdown said: If you want help you gotta be specific on what exactly you tried to do. hey sorry, i just want to use the ARC B580 to transcode my streams.
April 29, 20251 yr 1 hour ago, Benjamin Picard said: hey sorry, i just want to use the ARC B580 to transcode my streams. Right but what are the things you've tried to do that didn't work? It should just be as simple as adding --devices=/dev/dri to the extra parameters section of the template.
April 29, 20251 yr 19 minutes ago, MowMdown said: Right but what are the things you've tried to do that didn't work? It should just be as simple as adding --devices=/dev/dri to the extra parameters section of the template. Yeah i tried about everything hehe docker run -d --name='EmbyServer' --net='bp' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="EmbyServer" -e 'UID'='2' -e 'GID'='2' -e 'GIDLIST'='2,18' -e 'NEOReadDebugKeys'='1' -e 'OverrideGpuAddressSpace'='48' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8096]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/MediaBrowser/Emby.Resources/master/images/Logos/logoicon.png' -p '8096:8096/tcp' -v '/mnt/user/appdata/EmbyServer':'/config':'rw' --device='/dev/dri/' So i get the GPU detected in emby but, i can't have it enabled. Whatever i tried, here's my i get in emby hardware log. "DeviceIndex": 1, "DeviceInfo": { "VendorName": "Intel Corporation", "DeviceName": "Battlemage G21 [Arc B580]", "SubsytemVendorName": "Intel Corporation", "VendorId": 32902, "DeviceId": 57867, "SubsytemVendorId": 32902, "SubsytemDeviceId": 4352, "DevPath": "/sys/bus/pci/devices/0000:17:00.0", "DrmCard": "/dev/dri/card0", "DrmRender": "/dev/dri/renderD128", "IsEnabled": 1, "IsBootVga": 0, "Error": { "Number": 18, "Message": "Failed to initialize VA /dev/dri/renderD128. Error 18" } Always this Error 18. I tried with other emby dockers, i get the same error.
May 3, 20251 yr 11 hours ago, Benjamin Picard said: @MowMdown any idea ? Curious, if you open the docker console and type in ls -n /dev/dri do you see card0 and renderD128 ? Have you tried the beta version of emby?
May 3, 20251 yr 8 hours ago, MowMdown said: Curious, if you open the docker console and type in ls -n /dev/dri do you see card0 and renderD128 ? Have you tried the beta version of emby? Yes it's there. I tried the latest and beta branch. Also tried the other emby dockers. Could it be a problem directly in unraid or since the card is detected, it's a problem from emby?
May 3, 20251 yr 9 hours ago, MowMdown said: Curious, if you open the docker console and type in ls -n /dev/dri do you see card0 and renderD128 ? Have you tried the beta version of emby? Also tried this in the docker console / # vainfo Trying display: drm libva info: VA-API version 1.22.0 libva info: Trying to open /lib/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva error: /lib/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 18 vaInitialize failed with error code 18 (invalid parameter),exit / # Seems like it's iHD_drv_video.so that fails to initialize.
May 4, 20251 yr 8 hours ago, MowMdown said: What if you pass through only one specific gpu instead of just /dev/dri? I tried with renderD128 and also card0. With renderD128 i have the same error. With card0 it's getting a DRM error ( "Message": "Failed to open the drm device /dev/dri/renderD128")
May 4, 20251 yr Disable any tonemapping settings, and try again. I found this to be an issue. It works if I turn off tonemapping Edited May 4, 20251 yr by MowMdown
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.