Setting up GUI Desktop on a VM: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
(Very rough copy of my notes on setting up a cloud VM with a MATE desktop and VNC server with some links/wording added.)
No edit summary
Line 12: Line 12:
<li>install tightvncserver
<li>install tightvncserver
{{Command|sudo apt install tightvncserver}}
{{Command|sudo apt install tightvncserver}}
For details about using VNC servesr and clients see our docs on vnc [[VNC]].
For details about using VNC servers and clients see our docs on vnc [[VNC]].
</li>
</li>
<li>configuring tightvncserver
<li>configuring tightvncserver

Revision as of 17:31, 24 November 2020


This article is a draft

This is not a complete article: This is a draft, a work in progress that is intended to be published into an article, which may or may not be ready for inclusion in the main wiki. It should not necessarily be considered factual or authoritative.



These instructions are for the Ubuntu operating system:

  1. install MATE
    [name@server ~]$ sudo apt update
    [name@server ~]$ sudo apt upgrade -y
    [name@server ~]$ sudo apt install ubuntu-mate-desktop
    

    During the installation of the ubuntu-mate-desktop package it will ask you to choose the default display manager, a good option is lightdm. Installing the ubuntu-mate-desktop package can take a fair amount of itme (maybe something like 15-30 mins?).

  2. install tightvncserver
    Question.png
    [name@server ~]$ sudo apt install tightvncserver
    

    For details about using VNC servers and clients see our docs on vnc VNC.

  3. configuring tightvncserver
    Question.png
    [name@server ~]$ vncserver
    -> enter a password
    -> enter "n" for view-only password
    
    vncpasswd command can be used to change password later
  4. Open port 5901 and test connection (see OpenStack#Security_Groups security groups for more information about opening ports to your VMs with OpenStack). However, this is not secure as the data sent to and from your VM will not be encrypted.
  5. Connect using an SSH tunnel See SSH_tunnelling. There is an example of creating an SSH tunnel to a VNC server running on a compute node of one of our clusters here: VNC#Compute_Nodes
  6. Close port 5901. Once you have you are connecting to your VNC server using an SSH tunnel you no longer require port 5901 open so it is recommended that you remove this rule from your security groups. (see OpenStack#Security_Groups security groups for more information).
  7. To stop the vncserver
    Question.png
    [name@server ~]$ vncserver -kill :1