Announcing TurnKey Linux 12.0: 100+ ready-to-use solutions


Ladies and gentlemen, the 12.0 release is finally out after nearly 6 months of development and just in time to celebrate TurnKey's 4th anniversary. I'm proud to announce we've more than doubled the size of the TurnKey Linux library, from 45 appliances to over 100!

As usual pushing out the release was much more work than we expected. I'd like to chalk that up to relentless optimism in the face of vulgar practical realities and basic common sense. On the flip side, we now have 100+ appliances of which 60+ are brand spanking new. Lots of good new applications are now supported.

Despite all the hard work, or maybe because of it, working on the release was the most fun I've had in a while.

You look away and then back and suddenly all this new open source stuff is out there, ready for prime time. So many innovations and competing ideas, all this free energy. We feel so privileged to have a front row seat and not just watch it all play out but also be able to play our own small role in showcasing so much high-quality open source work while making it just a bit more accessible to users.

Unlike previous releases this latest release is based on Debian, not Ubuntu. We realize this may upset hardcore Ubuntu fans but if you read on, I'll try to explain below why "defecting" to Debian was the right thing for TurnKey.

What's new?

Deprecated appliances

  • AppEngine: With the addition of Go, we decided to split the Google App Engine SDK appliance into 3 separate language specific appliances (appengine-go, appengine-java and appengine-python).
  • Joomla16: 1.6 has reached end-of-life, and has been replaced with the Joomla 2.5 appliance.
  • EC2SDK: Insufficient amount of interest to warrant maintenance, especially now that the TurnKey Hub exists.
  • Zimbra and OpenBravo: Will be re-introduced once TurnKey supports 64bit architectures. Sorry folks. We're still working on that.

Changes common to all TurnKey appliances - the TurnKey Core

As most of you know TurnKey Core is the base appliance on top of which all other TurnKey appliances are built and includes all the standard goodies.

Most of the ingredients Core is built out of comes directly from the Debian package repositories. Thanks to the quality of packaging refreshing these is usually very easy. A handful (e.g., webmin, shellinabox) we have to package ourselves directly from upstream because they're not in Debian. That takes more work, but still usually not a big deal.

Then there are the parts of TurnKey we developed ourselves from scratch. They're our babies and giving them the love they need usually involves more work than all the other maintenance upgrades put together. The largest of these components is TKLBAM - AKA the TurnKey Linux Backup and Migration system.

Version 1.2 of TKLBAM which went into the release received a round of much needed improvements.

The highlights:

  • Backup
    • Resume support allows you to easily recover and continue aborted backup sessions.
    • Multipart parallel S3 uploads dramatically speed up how long it takes to upload backup archives to the cloud. Dial this up high enough and you can typically fully saturate your network connection.
  • Restore
    • Added embedded squid download cache to make it easier to retry failed restores (especially large multi-GB restores!) without resorting to suicide.
    • Fixed the annoying MySQL max_packet issue that made it unnecessarily difficult to restore large tables.

In a bid to open up development to the community we've also tried to make TKLBAM more developer friendly by making its internals easier to explore via the "internals" command. We've also put the project up on GitHub. For a bit more detail, read the full the release notes for TKLAM 1.2.

TurnKey 12.0 appliances available in 7 delicious flavors

Optimized Builds

  1. ISO: Our bread and butter image format. Can be burned on a CD and run almost anywhere - including bare metal or any supported virtualization platform.
  2. Amazon EC2: 1,414 Amazon EC2 optimized builds, spanning the globe in all 7 regions, in both S3 and EBS backed flavors. The Hub has been updated and all images are available for immediate deployment.
  3. VMDK / OVF: For those of you who like a slice of virtual in your lemonade, we've got VMDK and OVF optimized builds for you too.
  4. OpenStack: The new kid on the block, OpenStack optimized builds are just a download away, get 'em while they're hot. Oh, and don't forget that these builds require a special initrd.
  5. OpenVZ : Is OpenVZ your sweet tooth? Step right up! Using Proxmox VE? The TurnKey PVE channel has been updated as well for inline download and deployment right from your web browser.
  6. Xen: And who can forget about our favorite steady rock, optimized builds for Xen based hosting providers are at your fingertips.

Want just one appliance? Follow the download links on the site to download any image in any flavor individually from SourceForge.

Want to collect them all? Thanks to the good people manning TurnKey's mirror network, you can now get all the images in a particular image format (about 20 GB) or even the whole 120 GB enchilada.


  • 7 build formats
  • 606 downloadable virtual appliance images (120 GB worth)

Ubuntu vs Debian: the heart says Ubuntu, but the brains says Debian

One of the hardest things we had to do for this release was choose between Ubuntu and Debian. We initially planned on doing both. Then eventually we realized that would nearly double the amount of testing we had to do - a major bottleneck when you're doing a 100+ appliances.

Think about it. At this scale every one hour worth of extra testing and bugfixing translates into about 2-3 weeks of extra manwork. And to what ends? We already had way too much work to do, and the release kept getting pushed back, again and again, did it really matter whether we supported both of them like we originally intended? Would it really provide enough extra value to users to warrant the cost? They were after all quite similar...

In the end, choosing to switch over to Debian and abandon Ubuntu support for now was hard emotionally but easy on a purely rational, technical basis:

  1. Ubuntu supports less than 25% of available packages with security updates

    Remember that TurnKey is configured to auto-install security updates on a daily basis.

    This may sound dangerous to users coming from other operating systems but in practice works greats, because security updates in the Debian world are carefully back-ported to the current package version so that nothing changes besides the security fix.

    Unfortunately, if you're using Ubuntu there's a snag because Ubuntu only officially supports packages in its "main" repository section with security updates. Less than 25% of packages are included in the "main" repository section. The rest go into the unsupported "universe" and "multiverse".

    So if an Ubuntu based TurnKey appliance needs to use any of the nearly 30,000 packages that Ubuntu doesn't officially support, those packages don't get updates when security issues are revealed. That means users may get exposed to significantly more risk than with an equivalent Debian based TurnKey appliance.

    While Ubuntu are continually adding packages to its main repository, they can't keep pace with the rate of packages being added to Debian by thousands of Debian Developers. In fact, with each release the gap is growing ever wider so that an increasingly smaller percentage of packages are getting into main. For example, between Debian 6.0 (Squeeze) and the upcoming Debian 7.0 (Wheezy) release 8000 packages were added. In a comparable amount of time, between Ubuntu 10.04 (Lucid) and Ubuntu 12.04 only 1300 packages were added to main.

  2. Debian releases are much more bug-free and stable

    Stability wise, there's no comparison. Even the Ubuntu Long Term Support releases that come out every two years have serious bugs that would have held up a Debian release.

    Fundamentally this is due to the differences in priorities that drive the release process.

    Debian prioritizes technical correctness and stability. Releases are rock solid because they only happen when all of the release critical issues have been weeded out.

    By contrast, Ubuntu prioritizes the latest and greatest on a fixed schedule. It's forked off periodically from the Debian unstable version, also known as "sid" - the toy story kid that will break your toys. It then gets released on a fixed pre-determined date.

    There's no magic involved that makes Ubuntu suddenly bug-free by its intended release date compared with the version of Debian it was forked from. Ubuntu has a relatively small development team compared with Debian's thousands of developers. I think they're doing an amazing job with what they have but they can't perform miracles. That's not how software development works.

    So Debian is "done" when its done. Ubuntu is "done" when the clock runs out.

  3. Ubuntu's commercial support is not available for TurnKey anyhow

    Part of the original rational for building TurnKey on Ubuntu was Canonical's commercial support services. We theorized many higher-end business type users wouldn't be allowed to use a solution that didn't have strong commercial support backing.

    But 4 years passed, and despite talks with many very nice high level people at Canonical, nothing happened on the ground, except that one time Alon was invited to participate in an Ubuntu Developer Summit.

    We realized if we wanted to offer commercial support for TurnKey we'd have to offer it ourselves and in that case it would be easier to support Debian based solutions than Ubuntu.

Those were the main reasons for switching to Debian. Most of the people we talked to who cared about the issue one way or another preferred Debian for the same reasons, as did the majority of the 3000 people who participated in our website survey.

Don't get me wrong. Despite all the mud that has been slung at Ubuntu recently we still have a huge amount of respect for Ubuntu and even greater respect for the Ubuntu community. Sure, mistakes have been made, we're all only human after all, but let's not forget how much Ubuntu has done for the open source community.

Also, just because we don't have the resources to support Ubuntu versions of all TurnKey appliances right now doesn't mean we've ruled that out for the future. It's all about using the right tool for the job. If for some use cases (e.g., the desktop) that turns out to be Ubuntu, we'll use Ubuntu.

How to upgrade existing appliances to TurnKey 12

Simple: Just use TKLBAM to create a backup of an existing older version and then restore it on TurnKey 12.

TKLBAM only backs up files that have changed since the default installation. That means if you changed a configuration file on TurnKey 11.3 that configuration file will be backed up and re-applied when you restore to TurnKey 12.

What's next: opening up TurnKey, more developers = more appliances

To those inevitable number of you who will be disappointed that a favorite application hasn't made it into this release, please be patient, we're working within very tight resource constraints. I'll admit it's our own damn fault. We realized about a couple of years too late we haven't been open enough in the way we've been developing TurnKey.

Better late than never though. We're working very hard to fix this. Much of the work we've been doing over the last year has been to clean up and upgrade our development infrastructure so we can open it up fully to the community (and support additional architectures such as amd64!).

Soon anyone will be able to build TurnKey appliances from scratch using the same tools the core development team is using. We're working on this because it's the right thing to do as an open source project. We're also hoping it will help more people from the open source community contribute to TurnKey as equal members and lift the labor bottleneck that is preventing us from scaling from 100+ to a 1000+  TurnKey appliances.

Many, many thanks to...

  • Jeremy Davis, Adrian Moya, Basil Kurian, Rik Goldman (and his students), L.Arnold, John Carver, and Chris Musty. These guys submitted many TKLPatches that made it into this release, and even more importantly kept the community alive while we dropped off the face off the earth to focus on development.

    Their dedication and generosity have been an inspiration. We'd like the community to get to know them better so we'll soon be publishing interviews with them on the blog. Stay tuned.

  • Jeremy Davis AKA "The JedMeister": TurnKey forum moderator and all around super great guy. Jeremy is such an important part of what makes the TurnKey community tick I figured I should thank him at least twice. For emphasis. :)

  • The many rivers of upstream: Debian, Ubuntu and all of the wonderful open source communities who give love and write code for the software that goes into TurnKey.

  • Everyone else who helped test the 12.0 release candidate and provided ideas and feedback.

  • TurnKey users everywhere. Without you, TurnKey's audience, there really wouldn't be a point.


Chris Musty's picture

Huge round of applause and a toast to the best collection of dead easy appliances the world has ever seen!


Well done guys, love your work!

Chris Musty


Specialised Technologies

Luke Scammell's picture

I was just looking at the blog yesterday hoping there would be an update, so this is very welcome news!

Unfortunately, upon creating a fresh LAMP Stack on the hub (which worked great) and restoring a backup to it through Webmin, I get an error on mysql database restore and the backup restore halts before putting my actual site files on the server :/

This makes me nervous about the current web server's backups as well, in fact I think I may try a clone of the server and see if that works.

Any ideas? Here's the end of the log with the error:

table: website/wp_posts 
ERROR 1062 (23000) at line 20646: Duplicate entry '1' for key 'PRIMARY' 
Traceback (most recent call last): 
File "/usr/bin/tklbam-restore", line 385, in <module> 
File "/usr/bin/tklbam-restore", line 360, in main 
File "/usr/lib/tklbam/", line 124, in database 
limits=self.limits.db, callback=mysql.cb_print()) 
File "/usr/lib/tklbam/", line 449, in restore 
fs2mysql(mysql(), myfs, **kws) 
File "/usr/lib/tklbam/", line 412, in fs2mysql 
MyFS_Reader(myfs, limits, skip_extended_insert, add_drop_database).tofile(fh, callback) 
File "/usr/lib/tklbam/", line 406, in tofile 
database.tofile(fh, callback) 
File "/usr/lib/tklbam/", line 279, in tofile 
File "/usr/lib/tklbam/", line 345, in tofile 
IOError: [Errno 32] Broken pipe  

Strangely enough, if I run a mySQL export of the database in phpmyadmin (TKL LAMP Stack 11.3) and then import it to the new v12 one, it imports just fine...

Liraz Siri's picture

I managed to track this down to a bug in the mysql deserialization code that happens under just the right (or rather wrong) circumstances. A fix has been committed and will be pushed out to the archive soon. If you don't get the fix automatically just do this next week:

apt-get update 
apt-get install tklbam

We're discussing whether or not it would be a good idea to push this out as an automatic update to save users the trouble.

Tremendous apprectiation for all the hard work and time commitment: Present and future community will appreciate this for quite some time.

 606 images. Wow.

Congratulations. I really appreciate your hard work

Dennis Groves's picture

This is just pure awesome!!! Great job guys! :-D


Chris.Sonnier's picture

Been using Turnkey for a couple years now and it's really exciting to see some new appliances.  To everyone who has made this possible I can't thank you enough.  You all make our lives so much easier.

Now if I could only find the link to buy you guys another beer? I think it's been a while since I've bought a round, but this is much deserving.

Thanks Again!

Liraz Siri's picture

Hi Dan, sorry for the confusion. If you prefer searching for a string, I suggest you try the live appliance AJAX search widget I whipped up for the front page. It's the search bar right above the appliance grid.
Liraz Siri's picture

Thanks for the praise. It means a lot! From my work on the last release I can testify that despite certain worrying trends in certain parts of the web (e.g., the success of closed gardens such as Facebook and iTunes) there are still a huge number of people doing inspired work in the spirit of open source and free collaboration. They're just not getting the attention they deserve and I'm really hoping that's an area where TurnKey can help. At least with small but very important projects (e.g., Sahana Eden Ushahidi).

Don't worry. Tim Berner Lee's vision of a free web is alive and kicking. Closed gardens and proprietary innovations may blossom for a time, but I believe open systems will eventually sweep them away just like the web swept away AOL, CompuServe and MSN. And remember when Microsoft was feared by all? The bigger they get, the harder they fall...

L. Arnold's picture

Great work guys.  We can only imagine all the time and details that you have covered!  So much more to say, but the big one is THANK YOU!

Landis A.

Liraz Siri's picture

I know you probably don't care about this sort of thing, but I just realized I didn't mention you specifically in the thanks section. Face palm, you're one of TurnKey's top community members! I guess that's always a risk when you start mentioning people by name. Oh well, at least I fixed the blog post. Better late than never I guess.

But I digress. Thank you Arnold for helping to keep the community alive, and for all the great ideas and enthusiastic feedback!

Liraz Siri's picture

Keep up the awesome comments! :)
Hans Harder's picture

nice to see so many appliances...

I am going to test a few openVZ appliances in our LXC environment and see with how little adaptions I can make that working.. 

QUOTE:  ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol

Liraz Siri's picture

I'd be surprised if LXC doesn't turn out to be the future of lightweight virtualization for Linux. OpenVZ is great but it would be better if we could pull this off with features in the mainline kernel. Last time I looked LXC wasn't ready for prime-time as an OpenVZ replacement - it was still missing a few features and the isolation wasn't strong enough. You're probably more up-to-date on the current state of LXC so we'd be really interested in your experience getting TurnKey to work in that context. It might even lead to a new build format...
Jeremy Davis's picture

Once again my patience has been rewarded! :) I look forward to taking these new releases for a spin. You guys seriously rock!! The sheer volume of the appliance library now is incredible. So many of these I have never even heard of!

The additions/tweaks to TKLBAM sound excellent and making the code available on GitHub certainly opens it up that little bit more. I look forward to having a bit of a look at what 'internals' has to offer.

Whilst I am a little sad to see the back of Ubuntu servers (at least for now) I think I can come to terms with that. And your rationale makes perfect sense. Now for the 64 bit appliances!?!

My only trepedation in this announcement is that unless you have tricked up TKLBAM to specifically handle this change, whilst many appliances may well migrate without issue (from v11.x to 12.x) I would expect at least as many issues as there were going from TKL v2009.x to v11.x. Ie it won't be trouble free for all and certainly won't be "Simple: Just use TKLBAM to create a backup of an existing older version and then restore it on TurnKey 12." (Sorry to put a damper on all the enthusiasm, just saying it how I see it!) I anticipate that at least some appliances will require a bit of tinkering to get working nicely.

Regardless, it's a huge milestone in the TKL project and I am proud to be a part of it all. I'm a little disapointed with myself that I haven't been able to be more a part of the dev process behind the scenes over the last 6mths or so but at least I've been able to help out with the forums amongst all the business of life that keeps getting in the way of what I'd like to do...

And finally; beyond the thanks already written by Liraz above, I'd like to give a special mention to the new community members that have joined us along the way. Their expertise (especially in areas where I have none) and input to the forums has been invaluable to the community and in helping people with their issues. These people that are putting back in in an obvious way have made my life as a forum mod much, much easier (and made me feel much less lonely! :D). Thanks so much to all of you! There are a number of people that probably deserve to be named and thanked personally, but for fear of leaving someone out (and/or creating a list that rattles on for ever...) I'm only going to name one that particularly stands out (to me at least); Chris Musty. So thanks Chris for your enthusiasm and professional expertise and insight (I'm more of a hobbyist myself). And to all you others that I haven't named (and surely deserve it) thanks so much for all you've put in, making everyone's life that little bit easier and making the forums a friendly, helpful place to come.

Liraz Siri's picture

As GigaTux testified one of the really nice things about Debian is how smooth the upgrade process is between major releases. We have servers that started life out as Debian 4.0 (etch) almost 6 years ago and are now running squeeze and the process has always been very smooth. To make that happen you have to do a ton of testing and pay very close attention to details. Nobody besides Debian has the resources to pull that off successfully, not even billion dollar companies such as RedHat.

Unfortunately, this advantage will mostly apply to people upgrading from TurnKey 12.0. I agree that some tinkering may be required to get things to work, and I'm thinking of editing the blog post to reflect that but I don't think it will have much to do with the transition from Ubuntu to Debian. In fact, Ubuntu Lucid 10.04 forked off from the Debian unstable repository that turned into Squeeze not long after. Under the hood the package versions are actually closer than if TurnKey 12.0 was based on Ubuntu Precise 12.04.

Regarding participating in development "behind the scenes", that will become much easier once we finish our infrastructure revamp and open it up to the community. Until then don't underestimate how much you've helped just "hanging around in the forums". I shudder to to think what would have happened to the TurnKey community without your help. I've discovered we can get a huge amount of extra work done if we tune out the world and focus just on development, but we couldn't do that if it meant TurnKey would turn into a ghost-town.

Also, thanks for pointing out my conspicuous lack of recognition for Chris Musty's community involvement in recent months. It's a poor excuse but I've been buried under in development mode for too long. Update the blog post to give him the proper props!

Liraz Siri's picture

I feel like a chump for saying this, because we've really had 64-bit on our roadmap for so long it's kind of shameful. We wanted to have 64-bit appliances ready for the release but when that wasn't ready we decided not to delay any further and just make another announcement when they were ready. I'm pretty sure before the year is out we'll have 64-bit support. It's a top priority. Stay tuned!
Donovan Acree's picture

Not seeing 64bit support on the 12.0 release was a major dissapointment for me. I've been holding off on a TKL Zimbra server for a while now waiting for this release. 

Right now, it seems TKL has no email solution available. Here to hoping that changes very soon.

Hans Harder's picture

If you need help with something for the 64 Bit version, you should just ask.

I think plenty of people want to help out, if they know what is needed.

QUOTE:  ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol

Liraz Siri's picture

You don't have to marry TKLBAM. You can use it just to migrate your data from the old appliance to the new. You don't even have to upload anything to S3 because TKLBAM's backend (Duplicity) supports lots of other storage types, including the local filesystem. It just takes a bit more work to get it working. I recommend you experiment by migrating an fresh installation of 11.3 to a fresh installation of 12.0.
Jeremy Davis's picture

You do not need to use Amazon S3 storage if you don't want!? Personally I like to have local backups too, but S3 (the default TKLBAM storage) is cheap as chips (I currently have 8 appliances backing up with TKLBAM and my bill is literally a few cents per month) and allows you to take care of that essential offsite backup (assuming you care about your data) so easily.

To use local backup you will still need to set up an Amazon account (assuming you don't already have one) and the backup management is nowhere near as user-friendly (TKLBAM dash via the Hub makes it simple to see what, when and how much was backed up). But I can guarantee that if you run no backups to S3 then you won't ever be charged anything for TKLBAM (IIRC you may need to disable the automated backups to be certain). To be sure, you could even cancel your account after you do your migration if you desire.

If you haven't tried TKLBAM before, then I think now is the perfect time to give it a spin.

My only reservation though is that the migration using TKLBAM may still not be 100% flawless due to the diferences between versions of (upstream) software (some versions do things differently eg their database tables may be different). Many (most?) of the appliances will most likely be a straightforward migration. Even if it's not, most upstream software providers have at least migration notes/documentation, if not scripts (eg for adjusting DB schemas). But as I overlooked, and Liraz states, most of the core components (from Ubuntu repos in v11.x and Debian repos in v12.x) are virtually the same so should cause little to no issue, it's more the upstream installed software (eg Joomla jumps from v1.5  to 2.5).

Chris Musty's picture

I am currently doing video tutorials for different things TKL related.

There is quite a bit of contrent to get through but will be youtubing them soon.

The original thread is HERE

Chris Musty


Specialised Technologies

Ric Moore's picture

Excellent job! I get a kick out of your Aussie (?) accent! I figure if someone who basically lives upside down can do it, then I should be able to follow the instructions. /grins/ Ric

Liraz Siri's picture

We removed the donate button from the front page as soon as we had a better way to fund TurnKey development - the various premium services provided by the TurnKey Hub. Maybe that was a mistake but I was never comfortable soliciting donations - it kind of feels like panhandling. You can still find the donation link in the footer if you look hard enough but rather than tossing a few coins in the can, we'd rather people who want to give back give back not to us but to others in the TurnKey community. "Pass it forward" so to speak: help a damsel in distress on the forums, introduce a friend in need to TurnKey, file a bug report, share your ideas for TurnKey, develop a brilliant TKLPatch, etc.
OnePressTech's picture

I have been in the business of computing for 37 years and have worked on and managed the release of a number of global commercial communication appliance products. I have spent the last 6 months researching and working with a large number of commercial and open source cloud components.

I can say without reservation that the Turnkey Linux project and this release 12.0 is an astounding piece of work that is a key plank in any organisation's cloud mix. To have built this impressive library of technology with such a small team is just extraordinary.

It is with much appreciation for all the hard work that the TKL team put into this and previous releases that I would also like to extend my hearty congratulations.

Well done guys. Thank you.


Tim (Managing Director - OnePressTech)

Liraz Siri's picture

Thanks for the thumbs up. Sounds like you've gained a lot of valuable experience in the last 6 months. If you get any ideas on how we can improve TurnKey, speak up! We can't always respond immediately, especially when we're buried under in a development cycle, but a lot of our best ideas have come from the community.

I've looked at this at every angle and concluded that there's just no way to express how much there is to appreciate here (as much the product as the committed human labor that went into it).

Thank you for your commitment to a productive, active community whose feedback is not only welcome, but encourage and taken into account at every turn.

Jose Ordonez's picture

Don't worry Adam! I also thought that it was gone, but it got installed together with the packages. Whooh! And also a huge thanks from Mexico. A big up, and a cheers for all the hard work on this.

Greetings from Merida, Jose Ordonez.

PS. turnkeylinux rules!

Ric Moore's picture

You guys have saved my sanity, what there is left of it. If you EVER have an IPO, I want in. This is without a doubt the absolute best thing to happen to online computing since the modem. Again, thanks! I work for a non-profit and hope to educate others in the non-profit world how to use Turnkey. We have some fine minds, looking for work, who could make money installing and maintaining small web sites for those computer challenged in the non profit world. So, you may be the answer to prayers here. Ric

Jason Adams's picture

Thanks so much for all the work you put into all these applications. They're truly awesome and you've made my life so much easier.

I am having a problem, though, downloading LAPP 12 from Proxmox. I'm getting a "not found" error. Can you check to see if there's a typo? I'd like to download the new LAPP and upgrade Pg 8.4 to 9.1 (out of functional necessity).

Looking forward to playing around with all these! :D

Jeremy Davis's picture

Perhaps it's a problem with the SourceForge mirror that you are downloading from? It's working from my end.

If it continues to be a problem you could download it manually (OVZ template from the appliance page) and either upload it to PVE with the WebUI or SFTP to /var/lib/vz/template/cache.

Jason Adams's picture


Hey Jeremy!

I ended up downloading the ISO from the website and uploading it that way. I just like the convenience of downloading directly from within Proxmox. Oddly enough, I had no problem downloading the core.

Have the mirrors changed since 12 released? Is there a new mirror list I can download?


Jeremy Davis's picture

That would make sense actually because the mirror would be the same! The OVZ template is actually exactly the same file, whether you download manually or via PVE.

All the TKL images are hosted on SourceForge so I'm guessing it is a problem with whoever your closest SF mirror provider is. When you download a file from SF is runs a geo-location/bandwidth algorithm and then uses the closest/fastest mirror. Obviously for some reason or other whoever is mirroring SF files to you doesn't have the LAPP appliance OVZ (and for some reason isn't trying to mirror it).

Here is a link to download the LAPP OVZ where you can manually choose which SF mirror to use.

Ric Moore's picture

Is there anything out there to rival Quickbooks? I'd DEARLY love to see a Quickbooks killer. I want to get it out of our organization like they uproot Mandrake out of it's pot, screaming and shrieking, at Hogwarts. I'd settle for anything in the way of an accounting system. It's the only thing between me and a complete Turnkey setup. No more stinking licenses. We're handing the donations of little old Church Ladies to the World's Richest Man. Go figure. Jesus weeps. Ric

L. Arnold's picture

Old question but I thought I would respond. A few folks have made Patches it seems to OpenERP 7.  It is fantastic software and worth a try.  OpenERP 7 came out in mid Dec 2012.

Ric Moore's picture

Now THAT would make one helluva container!! They offer up the source code so I'm wondering if there are resftrictions to it's use by someone like Turnkey??

Jeremy Davis's picture

This is an old blog post which relates to a really old release. As such, it isn't super relevant anymore. As it seems to be attracting a lot of spam posts, I'm going to lock it. Please feel free to comment elsewhere or better still sign up and start a new thread.