Switch base distribution to Ubuntu 16.04 LTS Xenial Xerus #758
Comments
|
Ugh has it been two years already? I'm tempted to wait two more years and switch at what would presumably be 18.04 LTS.... |
|
I believe this is due to too much maintenance needed for MIAB either way? How could the community help out with a port / fork / migration path? On 15 March 2016 at 02:57, Joshua Tauberer [email protected] wrote:
|
|
So the first question is whether we want to force all existing users to kill their current boxes and set up a new one now or in two years? I don't want to maintain two branches, so once the next branch is released there won't be any further development on the old one (except critical security issues for some limited amount of time). |
|
Here's another idea, which may not be worth anything but is worth mentioning on the off chance it is: what about having only one branch, but implementing the support for 16.04 by adding conditionals in each place that 16.04 has to be treated differently to 14.04? This could be maintained for e.g. 9 months, giving users plenty of time to upgrade. At the end of that period, the conditionals could be removed and the scripts would revert to supporting only one Ubuntu version. I guess the feasibility of this would depend on how many things need to be changed for 16.04, and only experimentation will confirm that. |
|
I think what @dhpiggott is suggesting could work very well, as the main change with 16.04 is the usage of systemd. I've been running my personal installation on 15.10 for a while now and I had to change only a few things to get it working. The only thing I couldn't get working was the dovecot-lucene package. I certainly could do a PR once I've cleaned up my code. |
|
If it's that easy, yes, that would work. |
|
In my experience the live LTS updater is pretty unstable. However, I think it's worth a try for - as you often emphasize - unmodified boxes to do an in-place upgrade along with mail in a box. |
|
I've decided that we need a complete test suite before we change the base Ubuntu version (or anything more drastic). Otherwise we'll have no idea if the system is working properly on the new version. See #777. Thanks. |
JoshData
changed the title
|
Maybe it's worth considering something like NixOS. |
|
The problem with that is that it it stops being easy to use. Most cloud providers don't have readily-available images for NixOS. Customization, while discouraged, would also be harder; a lot of people consider dpkg the one Linux package manager and would probably be left confused. Not to mention the entire thing would need to be ported to an environment that is probably unknown to MiaB developers. |
|
Just a thought to reconsider shipping as a .deb if we ever make it to 16.04. #183 |
|
If you are happy to tie your self to Ubuntu then I would use snappy packages rather than deb for three reasons:
|
|
Before you go with snappy, you should be investing in plain old Docker. Wider adaptation, same features. I think the point is really to use what @JoshData is familiar with. |
:( |
|
I use Docker on Ubuntu 16.04 with this, and it works fine. |
|
@qinwf Have you gotten MIAB working in docker? That's been an ongoing struggle, so any insight you might have would be really valuable. |
|
Yes, I am using MIAB in a host with Ubuntu 16.04 with Docker image ubuntu-upstart:14.04. The mail works fine. One thing needs to take care of is that fail2ban does not work inside ubuntu-upstart:14.04. But it works in the host Ubuntu 16.04. I think this issue can be solved, but I did not try to solve it yet. |
|
A bunch of work was done to try to get MIAB running on docker. It was abandoned because it got too complex and didn't work quite right.
@qinwf If you have MIAB running in docker, that's awesome. Would you please share your changes back with the community?
Thanks!
… On Jan 23, 2017, at 12:10 AM, qinwf ***@***.***> wrote:
Yes, I am using MIAB in a host with Ubuntu 16.04 with Docker image ubuntu-upstart:14.04.
The mail works fine.
One thing needs to take care of is that fail2ban does not work inside ubuntu-upstart:14.04. But it works in the host Ubuntu 16.04. I think this issue can be solved, but I did not try to solve it yet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
It might be a better approach to develop and distribute mail-in-a-box using docker. See another dockerized mail server for example: https://github.com/andryyy/mailcow-dockerized |
|
what needs to happen for the 16.04/17.04 Upgrade: I'm asking because i would like to help. |
|
As I said above, the first thing is a test suite. There's some work on that in #1039 that we should get merged. |
|
I'm all for staying on 14.04 until 18.04 drops. There's only one catch that I can think of: https://help.ubuntu.com/community/UpgradeNotes So, unless something changes, 14.04->18.04 won't be supported. It needs to pass through each LTS release: 14.04->16.04->18.04. Would it be best to do both upgrades at the same time? Or should they be spread around a bit and done, say, a year apart? |
|
Also, as much as I would love love LOVE to move to Debian... Since it basically requires blowing away and re-provisioning the VM, I'm not sure it would ever be worth the effort. But I do hope somebody could tell me where I'm wrong. :) |
|
@jirislav I tried your fork on clean 16.04 LTS, but it looks like the installation did not complete. I am not able to access webadmin interface nor roundcube webmail. These are last messages before installation stopped. Installing Postfix (SMTP server)... |
|
Oh, I've probably incorporated an installation bug since my last stable version. Try this instead: |
|
Aww, I'm using NextClound under Stretch. I'm looking for a mail server but I would like to avoid usign docker, call me old school. Any method to install this without the nextcloud/nginx part? @jirislav is this "stable" enough? Any way to update later on future releases? |
|
@Extarys as long as I use this "stable" on my production server, I'll keep it up to date with original mail-in-a-box. I'm not considering moving to another mailserver solution anytime soon, because I'm satisfied with this |
|
That's enough for me ;) Thanks |
|
@jirislav I have set up your fork of MIAB and it is working fine in a Linode with 16.04.3 LTS. I had to use the details you posted on 11th Sept as I had the same problem as @bavicj with the most recent release. Just one question from a newbie. Now it is up and running what is the update procedure to keep it up to date? Thanks. |
|
@madera17 Update procedure is following:
cd mailinabox
git fetch --all
git checkout NAME_OF_THE_TAG_HERE
setup/start.sh |
|
@madera17 Oh, I'm sorry for that inconvenience with the Solr :( I plan to move the NextAnt + Solr upgrades to a separate module, which you will have the possibility to choose whether you want to install it or not, so that the main installation routine |
|
@Memphizzz I actually think it is already compatible with 18.04 :) .. I just have to try it out & fix problems that appear |
|
@jirislav Sounds good but keep in mind, 18.04 ain't released yet. The feature freeze didn't happen yet, so stuff might still change until the first of March. |
|
About install with Ubuntu 16 LTS 64-bit, some news? Can I use in it? ... Another option is to use a minimal hardware (ex. DigitalOcean droplet of 512Mb RAM 20 Gb HD and 1vCPU) with Ubuntu 14... There are some "minimal configuration" tips here? (no at README or site). |
|
Really??? |
|
@ilyaevseev really what? |
|
According to the ubuntu CVE on the meltdown exploit, 14.x won't be updated because it is EOL. It is of course possible there will be a backport, but... Any plans to address this issue? |
|
Sorry, think i mis-read this page: https://people.canonical.com/%7Eubuntu-security/cve/2017/CVE-2017-5754.html,
see the second entry below...
Package
Source: linux-lts-trusty (LP Ubuntu Debian)
Upstream:
needed
Ubuntu 12.04 ESM (Precise Pangolin):
pending
Ubuntu 14.04 LTS (Trusty Tahr):
DNE
Ubuntu 16.04 LTS (Xenial Xerus):
DNE
Ubuntu 17.04 (Zesty Zapus):
DNE
Ubuntu 17.10 (Artful Aardvark):
DNE
Ubuntu 18.04 LTS (Bionic Beaver):
DNE
Package
Source: linux-lts-wily (LP Ubuntu Debian)
Upstream:
needed
Ubuntu 12.04 ESM (Precise Pangolin):
DNE
Ubuntu 14.04 LTS (Trusty Tahr):
ignored (end-of-life)
Ubuntu 16.04 LTS (Xenial Xerus):
DNE
Ubuntu 17.04 (Zesty Zapus):
DNE
Ubuntu 17.10 (Artful Aardvark):
DNE
Ubuntu 18.04 LTS (Bionic Beaver):
DNE
…On Jan 4, 2018, 13:08 -0500, Michael Kroes ***@***.***>, wrote:
Do you have a link to that statement?
This shows it at pending. This doesn't mention 14.04 as not supported. 14.04 isn't EOL as far as I know.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Folks, please open a new issue to talk about a new security issue. |
|
Do we have mail-in-a-box for ubuntu 16.04? |
|
@patricmutwiri No, but as @jirislav pointed out, we might get a version for 18.04 once its released. |
|
Let me just head to iRedmail |
|
There are a lot of 404s via |
|
No 404s here. Suggest you create a dedicated ticket unrelated to this one. |
|
Closing in favor of #1358. |
any news ? 14.04 is ,,, little retro :) maybe 20.04 ? no sorry bad joke .. |
|
See #1358. |
and others
The preflight issues a hard check for the used Ubuntu distribution.
With
16.04arriving within a month and already having a beta.Are there plans to start a new branch
xxfor Xenial Xerus to prepare for the upcoming migrations?Häppy Hacking!
The text was updated successfully, but these errors were encountered: