> > You are absolutely right. > > The value comes from XAUTHORITY which is given to the container. Is > > it a > > wanted behaviour? > > I suppose this is coming from sysv init which does not take care of > cleaning up the env variables (which is better because we can transmit > env variables from the host to the container). > > Can you check XAUTHORITY is set in your container ? and ensure it is > set > before the vncserver is launched ?
Yes. vnc4server doesn't need an XAUTHORITY env entry but uses it if it is there. So simple solution: delete that or all env-entries in rc.local before execute vnv4server. Thx for your help. ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
