showkubii 0 Posted May 9, 2020 Share Posted May 9, 2020 (edited) ubuntu 20.04 LTS emby: image: emby/embyserver:beta container_name: emby environment: - PUID=1000 - PGID=1000 - GIDLIST=44 - TZ=Asia/Bangkok - UMASK_SET=022 volumes: - /mnt/config/emby:/config - /mnt/gmedia:/gmedia:ro - /tmp/transcoding:/transcode ports: - 8096:8096 - 8920:8920 devices: - /dev/dri:/dev/dri restart: unless-stopped Emby Premiere Lifetime No Chose /dev/dri Edited May 9, 2020 by showkubii Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted May 9, 2020 Share Posted May 9, 2020 (edited) I think devices: - /dev/dri:/dev/dri might need to be device: - /dev/dri:/dev/dri https://hub.docker.com/r/emby/embyserver And make sure your GIDLIST value is correct. Edited May 9, 2020 by mastrmind11 Link to comment Share on other sites More sharing options...
showkubii 0 Posted May 9, 2020 Author Share Posted May 9, 2020 (edited) I think devices: - /dev/dri:/dev/dri might need to be device: - /dev/dri:/dev/dri https://hub.docker.com/r/emby/embyserver And make sure your GIDLIST value is correct. docker - GIDLIST=44 correct or wrong ? Edited May 9, 2020 by showkubii Link to comment Share on other sites More sharing options...
Luke 37251 Posted May 9, 2020 Share Posted May 9, 2020 If you have Nvidia hardware then this might help: https://emby.media/community/index.php?/topic/76937-docker-hwa-nvidia-instructions/ Link to comment Share on other sites More sharing options...
showkubii 0 Posted May 10, 2020 Author Share Posted May 10, 2020 (edited) If you have Nvidia hardware then this might help: https://emby.media/community/index.php?/topic/76937-docker-hwa-nvidia-instructions/ I don't use Nvidia hardware I use cpu intel j3355 (Intel® HD Graphics 500) how to fix? Edited May 10, 2020 by showkubii Link to comment Share on other sites More sharing options...
Luke 37251 Posted May 10, 2020 Share Posted May 10, 2020 Currently our hardware transcoding support on Docker is only experimental. It will require some setup on your part and at this stage we may not yet have all of the answers. Have you configured the docker container to allow access to the graphics hardware? Link to comment Share on other sites More sharing options...
showkubii 0 Posted May 10, 2020 Author Share Posted May 10, 2020 (edited) Currently our hardware transcoding support on Docker is only experimental. It will require some setup on your part and at this stage we may not yet have all of the answers. Have you configured the docker container to allow access to the graphics hardware? emby: image: emby/embyserver:beta container_name: emby environment: - PUID=1000 - PGID=1000 - GIDLIST=44 - TZ=Asia/Bangkok - UMASK_SET=022 volumes: - /mnt/config/emby:/config - /mnt/gmedia:/gmedia:ro - /tmp/transcoding:/transcode ports: - 8096:8096 - 8920:8920 devices: - /dev/dri:/dev/dri restart: unless-stopped Edited May 10, 2020 by showkubii Link to comment Share on other sites More sharing options...
Solution wedgekc 12 Posted May 10, 2020 Solution Share Posted May 10, 2020 Maybe try adding 109 to GIDLIST in addition to 44. I'm on 18.04 and it is different. I also just use the Intel graphics and only get a value for getent group video. I also don't have render as a group owner: ls -l /dev/dri/drwxr-xr-x 2 root root 80 May 3 10:25 by-pathcrw-rw----+ 1 root video 226, 0 May 3 10:25 card0crw-rw----+ 1 root video 226, 128 May 3 10:25 renderD128 docker exec emby ls -l /dev/dricrw-rw---- 1 root 44 226, 128 May 3 03:25 renderD128 1 Link to comment Share on other sites More sharing options...
showkubii 0 Posted May 10, 2020 Author Share Posted May 10, 2020 Maybe try adding 109 to GIDLIST in addition to 44. I'm on 18.04 and it is different. I also just use the Intel graphics and only get a value for getent group video. I also don't have render as a group owner: ls -l /dev/dri/ drwxr-xr-x 2 root root 80 May 3 10:25 by-path crw-rw----+ 1 root video 226, 0 May 3 10:25 card0 crw-rw----+ 1 root video 226, 128 May 3 10:25 renderD128 docker exec emby ls -l /dev/dri crw-rw---- 1 root 44 226, 128 May 3 03:25 renderD128 Oh!!! working Thank you so much Thank you so much. Link to comment Share on other sites More sharing options...
Luke 37251 Posted May 10, 2020 Share Posted May 10, 2020 Great job! What exactly is showing up now? Link to comment Share on other sites More sharing options...
showkubii 0 Posted May 15, 2020 Author Share Posted May 15, 2020 Great job! What exactly is showing up now? Link to comment Share on other sites More sharing options...
Luke 37251 Posted May 16, 2020 Share Posted May 16, 2020 Thanks ! Link to comment Share on other sites More sharing options...
lundblad 7 Posted December 10, 2020 Share Posted December 10, 2020 On 5/10/2020 at 11:21 AM, wedgekc said: Maybe try adding 109 to GIDLIST in addition to 44. I'm on 18.04 and it is different. I also just use the Intel graphics and only get a value for getent group video. I also don't have render as a group owner: Where do you get 109 from? Link to comment Share on other sites More sharing options...
wedgekc 12 Posted December 10, 2020 Share Posted December 10, 2020 40 minutes ago, mopsiptv said: From the following statements, make sure the numbers that are returned are included in the GIDLIST variable for your docker statement. getent group video | cut -d: -f3 getent group render | cut -d: -f3 Here are the detailed instructions https://hub.docker.com/r/emby/embyserver Link to comment Share on other sites More sharing options...
lundblad 7 Posted December 10, 2020 Share Posted December 10, 2020 2 minutes ago, wedgekc said: From the following statements, make sure the numbers that are returned are included in the GIDLIST variable for your docker statement. getent group video | cut -d: -f3 getent group render | cut -d: -f3 Here are the detailed instructions https://hub.docker.com/r/emby/embyserver thanks for the reply, but these commands do not work on synology. I followed this guide too but it still does not work. https://blog.jpleva.cz/2019/09/emby-enable-hardware-acceleration-in.html I also tested with "privileged: true" = no hardware acceleration.. Link to comment Share on other sites More sharing options...
wedgekc 12 Posted December 10, 2020 Share Posted December 10, 2020 6 minutes ago, mopsiptv said: thanks for the reply, but these commands do not work on synology. I followed this guide too but it still does not work. https://blog.jpleva.cz/2019/09/emby-enable-hardware-acceleration-in.html I also tested with "privileged: true" = no hardware acceleration.. Well, I haven't used Synology before, so I'm not really sure. I know some models don't use Intel cpus and thus will not have VAAPI acceleration. You may also need to install video drivers etc, I just don't know. What does "vainfo" return? Also check out other topics.. Link to comment Share on other sites More sharing options...
lundblad 7 Posted December 10, 2020 Share Posted December 10, 2020 41 minutes ago, wedgekc said: Well, I haven't used Synology before, so I'm not really sure. I know some models don't use Intel cpus and thus will not have VAAPI acceleration. You may also need to install video drivers etc, I just don't know. What does "vainfo" return? Also check out other topics.. I tested that also. hardware acceleration works for me in plex. Link to comment Share on other sites More sharing options...
wedgekc 12 Posted December 10, 2020 Share Posted December 10, 2020 3 minutes ago, mopsiptv said: I tested that also. hardware acceleration works for me in plex. What do the logs say? Link to comment Share on other sites More sharing options...
Luke 37251 Posted December 10, 2020 Share Posted December 10, 2020 Yes please attach the emby server log and hardware detection log. Thanks. Link to comment Share on other sites More sharing options...
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