{"id":26888,"date":"2019-12-15T20:12:25","date_gmt":"2019-12-15T20:12:25","guid":{"rendered":"https:\/\/home.apeconsulting.co.uk\/adrian\/?p=26888"},"modified":"2019-12-15T22:29:00","modified_gmt":"2019-12-15T22:29:00","slug":"freenas0-virtualisation","status":"publish","type":"post","link":"https:\/\/home.apeconsulting.co.uk\/adrian\/freenas0-virtualisation\/","title":{"rendered":"FreeNAS0 – Virtualise"},"content":{"rendered":"\n
\"Ubuntu<\/figure>\n\n\n\n

Although I might still try and get my old crashplan VM running on FreeNAS0, I always had it in my mind that I’d virtualise main use cases – ONLYOFFICE Document Service, Crashplan and Docker – on Ubuntu 18.04 on FreeNAS0.<\/p>\n\n\n\n\n\n\n\n

Creating the Virtual Machine(s)<\/h4>\n\n\n\n

Creating the VM in FreeNAS is pretty straight forward from the WUI, and then going through the standard Ubuntu installation process. Nothing fancy, just a server install with pretty much the default options plus SSH. You can then VNC into the server from the FreeNAS WUI.<\/p>\n\n\n\n

My first task was to set a root password, as it just makes it easier to install everything. Otherwise, I just forget to type sudo<\/code> on every line! That’s as simple as sudo passwd root<\/code> and then entering a UNIX password. Test it with su root<\/code> and the password. I’m going to set it so that I can SSH using root with the following:<\/p>\n\n\n\n

sudo sed -i 's\/#PermitRootLogin prohibit-password\/PermitRootLogin yes\/' \/etc\/ssh\/sshd_config
sudo service ssh restart<\/code><\/p>\n\n\n\n

I’m also going to be connecting to several NFS shares so need to install the NFS package apt install nfs-common<\/code> and then add mount points into nano \/etc\/fstab<\/code> which look something like this:<\/p>\n\n\n\n

192.168.n.n:\/mnt\/APEpool0\/temp \/mnt\/temp nfs nfsvers=3<\/code><\/p>\n\n\n\n

ONLYOFFICE<\/h4>\n\n\n\n

I blogged about getting ONLYOFFICE up and running in a VM here<\/a> (I knew this blog would start to come in handy!) and the main thing you need to install ONLYOFFICE in a VM is here<\/a>.<\/p>\n\n\n\n

It still works pretty well, and is mainly just a case of copying and pasting the lines into a terminal SSH session. Don’t try and be clever by changing the username or password, as it won’t work! It does warn you, but sometimes it’s easy to skip past the instructions and get carried away copy & pasting!! It also didn’t like installing npm<\/code> but this can be updated later.<\/p>\n\n\n\n

Once it was up and running, I updated the nodejs which includes npm<\/p>\n\n\n\n

curl -sL https:\/\/deb.nodesource.com\/setup_9.x | sudo bash -<\/code>

sudo apt-get install -y nodejs<\/code>

sudo apt-get install onlyoffice-documentserver<\/code><\/p>\n\n\n\n

After that, you can also rebuild the spellchecker as described, but if you get a permission issue with npm, you might need to read this<\/a>.<\/p>\n\n\n\n

Because I’m using this with an SSL secured Nextcloud, I also need to switch this to HTTPS, as described here<\/a>. All my certificates are managed in a jail, so I’ve mounted that into this VM and then configured the .conf file restarting NGINX. I think I’m going to leave that running in its own VM for now, and have different VMs for different things, rather than 1 doing everything.<\/p>\n\n\n\n

CrashPlan<\/h4>\n\n\n\n

I found this<\/a> which describes installing a light-weight desktop on Ubuntu server, as sometimes it’s just easier to see what’s happening. It’s certainly much easier to install and configure CrashPlan with it.<\/p>\n\n\n\n

I ended up going for the Lubuntu Core Server Desktop, and installation was as simple as the guide. It is very light, so much so it doesn’t even install a web browser!<\/p>\n\n\n\n

I copied across all of the mounts from \/etc\/fstab<\/code> on FreeNAS1, and configured them for the shares on FreeNAS0. All good apart from my poor typing skills which stopped a couple from starting to begin with!<\/p>\n\n\n\n

Installing CrashPlan and configuring it is pretty simple, but the terminology they use is pretty confusing! This<\/a> explains how to log into the CrashPlan service and then this<\/a> explains how to replace a device, although these are the steps I took:<\/p>\n\n\n\n