On Thursday, August 2, 2018 at 12:37:50 AM UTC+2, Alex Huang wrote:
>
> Actually, sorry, I misunderstood the situation. Propagating
> /tmp/.X11-unix and ~/.Xauthority is necessary for running a DE from a
> docker container. But in Sy, $HOME and /tmp are mounted already so you
> don't need to bind that.
That's what I thought, too.
> In my test, I can start Xfce from within the container. The panel has
> broken icons but the DE seems functional otherwise. I assume this is
> what you are seeing. My guess is the broken icons can be fixed with a
> bind to a cache directory. I get the same kind of broken icon problem
> in VBox when the VM has no more space.
Indeed that's what happens with Xfce in my case too. In KDE, Plasma is
crashing, so start menu and panels are missing from the taskbar.
Something alike happens with Gnome too. In each case, environment is
useful, in the sense that one can use right-click menu to reach "run
command" dialog, then start terminal, and run applications from there.
However, there are further issues with some applications, for example
while Firefox works fine, Emacs is crashing.
As far as using VNC server concerned, I'd prefer to avoid this. The
idea would be everything to be transparent for the end-user, that should
just login under given username, and end up in an container environment
that looks completely the same like under native Linux distribution.
Mounting $HOME and /tmp is perfectly fine in my case too. I have
experience with Singluarity only, and strictly in the domain of HPC, so
- could anyone advise is something alike maybe easier to accomplish with
Docker?