EEVEE not working on Azure VM docker container - Unable to open a display
Closed this issue · 6 comments
@juniorxsound
First of all thank you for the support you all are providing through this repo. When i tried mounting the device on Azure VM i ran into below error. I'm using Ubuntu 18.04, blender 2.92 and Docker version 20.10.5, build 55c4c88.
Below shows the GPU setup of my remote server.
Initially when i ran the sh file (here) it showed below error:
xauth: file /root/.Xauthority does not exist
xauth: (argv):1: unable to read any entries from file "(stdin)"
Then i created .Xauthority file using below commands
touch ~/.Xauthority
xauth generate $DISPLAY . trusted
But it gives an error ===> xauth: (argv):1: unable to open display "."
Could you please help me on why these errors are generated and also on how to create a DISPLAY for the remote server?
Hi @sridhar-gajjela, you are welcome, and thanks for the info!
I have seen this error happen before when running on a machine that doesn't have access to OpenGL (which is required to run Eevee).
I haven't tried running the Blender containers on Azure, but quickly looking at these docs, it seems you might have to get a specific instance (NV-series and NVv3-series) - is that what you are using? Does Cycles GPU rendering work for you?
Hi @juniorxsound Thank you for responding.
Yes, Cycles GPU rendering is working fine. The only problem is with EEVEE rendering. I'm using NCasT4_v3-series as this is cost optimal GPU VM for my use case.
I've followed this to make EEVEE work on this VM but i'm not sure if this is the correct (best) way to do. Can you please share your views on this?
That link you shared looks good to me, it's probably worth trying out an Azure NV-series and NVv3-series instance - would you be able to try it out?
@juniorxsound
I haven't tried it on NV-Series yet as it costs us a lot. I'm trying to automate the process that worked for me on NCasT4_v3-series. But i will give it a try as well. Thank you
Sounds good @sridhar-gajjela 🙏 closing this issue for now, but if you see the problem persisting or have any other context feel free to open a new issue/reopen this one!