You are here
v18.0 Stable Release #3 - 10 Updated ISOs & Hub Builds - Proxmox/LXC builds
We have the 3rd v18.0 stable release batch ready to roll (see all v18.x related announcements here). This batch brings the total number of v18.0 stable releases so far to 23! As per usual, it's taking longer than I would like, but they are coming together.
This release consists of 10 freshly updated and tested v18.0 appliances. This release includes all v18.0 LXC/Proxmox builds to date, as well ISOs and Hub builds. A few Proxmox users have reported success with the Proxmox/LXC builds but if you have any feedback, please share. It's still unclear when we might have other builds available, although a VMware user has stuck up their hand to assist with testing; so hopefully we may have them ready soon.
As per usual, these updated appliances can all be found on our mirror network, downloaded from their relevant appliance pages (links below) or they can be launched directly from the Hub (note that 17.x appliances are still the default for now - please see the first announcement for launching v18.0 apps).
v18.0 Update batch details
Beyond the inclusion of LXC/Proxmox templates, the only things of note for this release are a couple of bugfixes.
The first was the realization that the appliance hash files did not include the key download URL:
1. Verify the authenticity of this file by checking that it is signed with our GPG release key: $ curl | gpg --import
It should look like this:
1. Verify the authenticity of this file by checking that it is signed with our GPG release key: $ curl https://raw.githubusercontent.com/turnkeylinux/common/18.x/keys/tkl-bookworm-images.asc | gpg --import
This was a gross oversight on our behalf and it was only because a user got a corrupt download (which they reported) and in troubleshooting that, I discovered the missing URL. We won't rebuild the previous 13 to fix their hash files, but the updated code will mean all apps moving forward will include that URL. The above code block (the one with the URL after the curl command) can be used if you wish to download the key - the remaining instructions (i.e. checking the hash and that the file is properly signed) are correct.
The second bug, was that Webmin no longer included a log viewer. In previous TurnKey releases (i.e. v17.x and earlier) we used Syslog (technically Syslog-ng) for system logging. However in v18.x (based on Debian 12/Bookworm) Syslog is no longer required. Instead Journalctl (a component of systemd) provides all system logging requirements. However, I completely overlooked that removing Syslog (and Webmin-syslog) left Webmin with no facility for viewing logs! Oops. From this batch forwards, we are including webmin-logviewer - that allows you to view the journal, thus providing the required functionality. As per the hash bug, we're not going to rebuild the previous apps yet, but this batch and all others moving forward will include this package by default.
If you already have any of the other v18.0 appliances that don't already include the Webmin logviewer, you can easily install it from apt - either via Webmin (System >> Software Packages >> Install New Package -> Package from apt "webmin-logviewer") or the Webmin console or CLI (e.g. via SSH):
apt-get update apt-get install -y webmin-logviewer
v18.0 Apps updated this release
Here are the updated apps in this batch:
BookStack |
ConcreteCMS |
DokuWiki |
NGINXPHPFastCGIServer |
Nodejs |
Omeka |
osCommerce |
Prestashop |
SilverStripe |
WordPress |
All v18.0 apps to date
Whilst it's perhaps a bit redundant this time (as we've only release Core & TKLDev previously), as per existing convention, please find all the appliances (in alphabetical order) that have been released for v18.0 so far listed below:
Give them a try and share your feedback
We always love feedback. Hearing nice things is always great, and very valuable. Although constructive criticism is probably even better. So if you have any feedback, want to offer a hand with testing or would like to request a specific appliance be prioritized, please post below (guest posts don't require log in, but do require manual approval). Or you can open a new thread in the forums. Please note that posting new threads requires a free website user account; due to spammers, automated approvals have been disabled. So please ping me (via email, as a guest comment here, or over on the specific "welcome" thread) if you're waiting for approval.
If you think that you've found a bug or would like to request a new feature, please post below, in the forums or skip straight on over to our issue tracker (requires free GitHub user account).
Comments
Version 18.x Odoo App
Hi Jeremy,
Is there any schedule for v18.x Odoo App?
If so, what Odoo version will be installoed by defaut?
Regards,
Carlos Vercelino
Hi Carlos, yes it is coming
Hi Carlos, yes a v18.x Odoo appliance is coming... Although as you can see, the v18.x release is dragging quite a bit. Part of the issue is that we're introducing some automated smoke testing as we go. That's slowing down this release significantly, but we're hoping that will speed up future releases. (fingers crossed...).
As for what version, we had intended to stick with the Debian package for v18.x, but unfortunately it didn't make it into Debian 12/Bookworm. :( Although I note that Odoo-16 is in bookworm-backports, so my inclination is to go with that. Happy to have feedback from you (and anyone else) regarding that.
If this is one you're waiting for, I can try to get it int the next batch (actually it will be the batch after, the next batch is done and will be published early next week).
Hi Jeremy, yes I am expecting Odoo v16
Hi Jeremy, yes I am expecting Odoo v16, however if you for any reason opt for Odoo v17, I can go with it :)).
Just now, I will start using Odoo v16 (I am currently using Odoo v15 on an Odoo appliance v17.1), and install it on an Odoo appliance v17.1 (fingers crossed...) while v18 is not ready.
Regards
Carlos Vercelino
Pages
Add new comment