Christian's picture
Christian - Thu, 2016/11/17 - 23:02

Hello,

as per this announcement, a Turnkey Drupal 8 appliance exists. It is also announced in the ProxMox 4 LXC template section. However, download of the template fails, i.e. the URL

http://mirror.turnkeylinux.org/turnkeylinux/images/proxmox/debian-8-turnkey-drupal8_14.1-1_amd64.tar.gz

does not exist. Has the file been removed by accident or on purpose?

Thank you.

Forum: 
Support
Tags: 
lxc proxmox
drupal8
Jeremy Davis's picture

Jeremy Davis - Fri, 2016/11/18 - 00:40
Thanks for the nudge!

We pulled it from the mirror some time ago as it appeared that there was a critical security vulnerability in Drupal8. However on closer inspection it was actually a PHP/Apache vulnerability which had been patched by Debian (and would be auto installed by the pre-configured auto-security updates).

In retrospect I should have still publicly announced it and in future if something similar happens again I certainly will! But the long and the short of it is that I got sidetracked (it's been a crazy busy year) and never rebuilt and republished it as I had planned to. Until now, no one has explictly asked about it and I've been crazy busy so it's kept getting pushed back...

I'll ensure it rises up my "todo" list but I'm not 100% sure when I will get to it.

In the meantime you could build it yourself!? The tools we use to build the images are all freely available via GitHub.

First you'll want to download the TKLDev ISO (it won't work in a container so you'll need to install to a VM). I suggest that you give it at least 2 CPUs & 1GB RAM (more is better). Then have a look at this tutorial to get started. Once you've had a bit of a play and are ready to move on (or if you're impatient and want to just dive in) you can then clone the Drupal8 source code (as per docs). Unless you want to, you can skip building the Drupal8 ISO at this point, as you'll need to do it again with buildtasks below anyway...

Once you've done that, you'll need to install buildtasks as per the (pretty rough) documentation. Follow the instructions for buildtasks and you'll need to satisfy the requirements for bt-iso and bt-container as well. Create your config files as per the config section. Note that as you aren't uploading images to Amazon (as we do) then you don't need to adjust any of that stuff and (IIRC) can just copy them as they are.

The the final step is to build the ISO (with the bt script) and then the container. FWIW when we do a release, we build all the ISOs first, then process the ISOs to create all the other builds. That ensures that the alternate builds are all consistent with the ISO (and the other alternate builds).

So the last bit is: 

cd /turnkey/buildtasks
./bt-iso drupal8
./bt-container drupal8

Once that's done (it'll take a little while - probably about 20-30 mins all up), then there should be a fresh TurnKey Drupal 8 appliance container in /mnt/builds. E.g. /mnt/builds/container/debian-8-turnkey-drupal8_14.1-1_amd64.tar.gz

Christian's picture

Christian - Fri, 2016/11/18 - 15:42

I would love to try to build the appliance myself, however, I don't think I'll find the time at the moment. But great that you have described the process in detail so when I have time, I'll be happy to try that out. Please let us know when you get to add the Drupal 8 Appliance eventually.

Jeremy Davis's picture

Jeremy Davis - Thu, 2016/11/24 - 06:47

I anticipate that we'll probably do a batch build of a few appliances soon so will probably just announce it via the blog.

It looks like you are signed up to the "security and news" newsletter already, but if you want to get immediate notifications about blog posts, then you can subscribe to them too. When you're logged in, go to the blog page and towards the top right you should see text that says "Subscribe | By Email". If you click the "By Email" you can sign up to get email notifications of new blog posts.

Christian's picture

Christian - Sat, 2016/12/10 - 21:54

Hi Jeremy,

I did it and it worked very well. I have a working Drupal 8 LXC template now.

It wasn't so hard after all thanks to your detailed instructions. 

One small hiccup: 

[...]
Install the project...
-- Install configuration: ""
-- Installing: /usr/local/include/
-- Installing: /usr/local/include//PfffCLib.h
-- Installing: /usr/local/include//file_utils.h
-- Installing: /usr/local/include//PfffOutputFormatter.h
-- Installing: /usr/local/include//PfffOptionManager.h
-- Installing: /usr/local/include//PfffPostHashing.h
-- Installing: /usr/local/include//PfffOptions.h
-- Installing: /usr/local/include//output_utils.h
-- Installing: /usr/local/include//PfffFindDuplicatesOptionManager.h
-- Installing: /usr/local/include//PfffHttpBlockReader.h
-- Installing: /usr/local/include//PfffHasher.h
-- Installing: /usr/local/include//PfffBlockReader.h
-- Installing: /usr/local/include//PfffFtpBlockReader.h
-- Installing: /usr/local/include//PfffBlockSampleGenerator.h
-- Installing: /usr/local/./README.txt
-- Installing: /usr/local/./COPYRIGHT.txt
-- Installing: /usr/local/bin/pfff
-- Installing: /usr/local/bin/pfff-find-duplicates
-- Installing: /usr/local/lib/static/libpffflib.a
-- Installing: /usr/local/lib/static/libpffflib-static.a
./bt-container: line 61: /usr/local/src/pfff/build/config/common.cfg: No such file or directory

I could fix it by 

mkdir -p /usr/local/src/pfff/build/config
cp config/common.cfg /usr/local/src/pfff/build/config/

Might be something that has to be fixed in the script.

Thanks so much!

 

 

Jeremy Davis's picture

Jeremy Davis - Mon, 2016/12/12 - 03:52
Glad to hear it all worked out and was as daunting as it may have first appeared.

And thanks for the bug report. We'll need to look into that for the v14.2 release.

Add new comment