This post was written before FreeNAS Corral got memory-holed. I’ve not decided on my course of action yet. I like running my services in Docker far more than I ever liked JAILS and the LinuxVM, so going backwards is not really an option.
I recently upgraded my FreeNAS 9.3 box to FreeNAS 10, FreeNAS Corral. The upgrade was very smooth, although I did panic at one point when it took 500 years to boot back up.
I knew that the old Plugin system had been removed, and that Docker Support was the new way to get your plugins working. I had several plugins I needed:
The Linux VM plugin, or Jail, was what was letting me run an Ubuntu Server to host Squeeze Server. The Linux VM VirtualBox was not available any more, so the Squeeze Server would have to find a new home. Fortunately, there is a Docker Image for Squeeze Server.
Getting an Owncloud container running was pretty trivial. I did the following:
Create a new Dataset, for Owncloud Data to live in
Create the Owncloud Docker Container
- Give it a name
- Map the Dataset to the container path
- Set the Container to Bridged Mode. This is definitely possible with NAT, but I prefer having unique IP addresses for each container.
- Save the container, and start it up.
Once Owncloud has started up, I let it do a first time setup, letting it host the database itself, etc.
Migrating the Data from the Owncloud Jail
I needed to use the command line for this.
First, stop the container.
Copy the owncloud Jail data to the new Dataset.
My owncloud data was in /mnt/<Pool>/jails/owncloud/media
This location contained the User’s directories and the database, but not the config file.
Copy everything in here to your new Dataset, into the “data” folder:
That’s the data, but you need to edit the Config file as well. The config file for the new owncloud install is here:
You’ll need to replace this with the older config file from the plugin, which is here on my setup:
You might need to update the trusted domains to include your new Owncloud Docker IP (or the FreeNAS IP and Docker Port, if you’re using NAT).
After you’ve done this, you should be able to start the Owncloud Container and log in using your original credentials.
SSL, Let’s Encrypt, Reverse Proxies
This was hard work. The actual solution is not complicated, but there’s no single guide to tell you how to do it.
Nextcloud recommends that you use a Reverse Proxy to get SSL working for your NextCloud container. Owncloud is pracitcally the same thing, so it seems like the thing to do in both cases.
I use Letsencrypt for my certs, and previously I ran certbot from inside the Owncloud Jail. I initially assumed I would do the same thing here, but luckily for me the FreeNAS docker collection includes a Letsencrypt Image that includes NGINIX, which would let me set up a reverse proxy as well.
Things to keep in mind before you start:
-Port forwarding on your Router should already be set up for the domain name you want to create the Certificate for.
-you need a writeable area for the certificates. I have a dataset setup with “www” permissions specifically for this.