Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch base distribution to Ubuntu 16.04 LTS Xenial Xerus #758

Closed
almereyda opened this issue Mar 15, 2016 · 70 comments
Closed

Switch base distribution to Ubuntu 16.04 LTS Xenial Xerus #758

almereyda opened this issue Mar 15, 2016 · 70 comments

Comments

@almereyda
Copy link

@almereyda almereyda commented Mar 15, 2016

The preflight issues a hard check for the used Ubuntu distribution.

With 16.04 arriving within a month and already having a beta.

Are there plans to start a new branch xx for Xenial Xerus to prepare for the upcoming migrations?

Häppy Hacking!

@JoshData
Copy link
Member

@JoshData JoshData commented Mar 15, 2016

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....

@almereyda
Copy link
Author

@almereyda almereyda commented Mar 15, 2016

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 notifications@github.com wrote:

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....


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:

#758 (comment)

@JoshData
Copy link
Member

@JoshData JoshData commented Mar 15, 2016

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).

@dhpiggott
Copy link
Contributor

@dhpiggott dhpiggott commented Mar 15, 2016

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.

@ianberinger
Copy link
Contributor

@ianberinger ianberinger commented Mar 16, 2016

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.

@JoshData
Copy link
Member

@JoshData JoshData commented Mar 16, 2016

If it's that easy, yes, that would work.

@acuteaura
Copy link

@acuteaura acuteaura commented Mar 18, 2016

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.

@JoshData
Copy link
Member

@JoshData JoshData commented Mar 31, 2016

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 JoshData changed the title Ubuntu 16.04 LTS Xenial Xerus Switch base distribution to Ubuntu 16.04 LTS Xenial Xerus Apr 6, 2016
@ponychicken
Copy link
Contributor

@ponychicken ponychicken commented Apr 26, 2016

Maybe it's worth considering something like NixOS.
It is completely based around a declarative configuration.
You specify what services you want and how they should be configured,
and it takes care of building everything.

http://nixos.org/nixos/about.html

@acuteaura
Copy link

@acuteaura acuteaura commented Apr 26, 2016

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.

@JoshData
Copy link
Member

@JoshData JoshData commented May 19, 2016

Just a thought to reconsider shipping as a .deb if we ever make it to 16.04. #183

@anoma
Copy link
Contributor

@anoma anoma commented May 20, 2016

If you are happy to tie your self to Ubuntu then I would use snappy packages rather than deb for three reasons:

  1. in theory they let you roll back (something a .deb will never do)
  2. containerization like security
  3. but mainly you have far more control over the publishing process and you will not need to maintain your own repo or be beholden on official repo maintainers for fast turn around. The power to push and pull versions will be yours.
@acuteaura
Copy link

@acuteaura acuteaura commented May 20, 2016

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.

@JJJ
Copy link

@JJJ JJJ commented Jul 29, 2016

if we ever make it to 16.04

:(

@qinwf
Copy link

@qinwf qinwf commented Dec 9, 2016

I use Docker on Ubuntu 16.04 with this, and it works fine.

@cromulus
Copy link
Contributor

@cromulus cromulus commented Jan 23, 2017

@qinwf Have you gotten MIAB working in docker? That's been an ongoing struggle, so any insight you might have would be really valuable.

@qinwf
Copy link

@qinwf qinwf commented Jan 23, 2017

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.

@cromulus
Copy link
Contributor

@cromulus cromulus commented Jan 23, 2017

@bvdlingen
Copy link

@bvdlingen bvdlingen commented Mar 12, 2017

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

@e-fu
Copy link

@e-fu e-fu commented Apr 5, 2017

what needs to happen for the 16.04/17.04 Upgrade:
Is there a todo list?
Is an switch to Debian an option?

I'm asking because i would like to help.

@JoshData
Copy link
Member

@JoshData JoshData commented Apr 5, 2017

As I said above, the first thing is a test suite. There's some work on that in #1039 that we should get merged.

@bronson
Copy link
Contributor

@bronson bronson commented Apr 12, 2017

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?

@bronson
Copy link
Contributor

@bronson bronson commented Apr 12, 2017

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. :)

@bavicj
Copy link

@bavicj bavicj commented Sep 11, 2017

@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)...
Installing Dovecot (IMAP server)...
Creating new user database: /home/user-data/mail/users.sqlite
Installing OpenDKIM/OpenDMARC...
Installing SpamAssassin...
Installing Nginx (web server)...
Installing Roundcube (webmail)...
Installing Nextcloud (contacts/calendar)...
Upgrading to Nextcloud version 12.0.2
Installing solr version 6.6.0`

@jirislav
Copy link

@jirislav jirislav commented Sep 11, 2017

Oh, I've probably incorporated an installation bug since my last stable version. Try this instead:

git clone https://github.com/jirislav/mailinabox.git
cd mailinabox
git checkout v0.23a-ubuntu16-rc1
setup/start.sh
@Extarys
Copy link

@Extarys Extarys commented Sep 24, 2017

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?

@jirislav
Copy link

@jirislav jirislav commented Sep 25, 2017

@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

@Extarys
Copy link

@Extarys Extarys commented Sep 25, 2017

That's enough for me ;) Thanks

@madera17
Copy link

@madera17 madera17 commented Nov 4, 2017

@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.

@jirislav
Copy link

@jirislav jirislav commented Nov 4, 2017

@madera17 Update procedure is following:

  • Check out new releases
  • if there is tag with newer version than you have (it has to contain ubuntu16 in it's name), then execute these commands to upgrade:
cd mailinabox
git fetch --all
git checkout NAME_OF_THE_TAG_HERE
setup/start.sh
@madera17
Copy link

@madera17 madera17 commented Nov 5, 2017

@jirislav Thank you for the info.
Unfortunately when attempting to upgrade 'git checkout v0.24-ubuntu16' after running 'setup/start.sh' it ends as described by @bavicj with the last line -

Installing solr version 6.6.0`

Setup appears not to complete.

@jirislav
Copy link

@jirislav jirislav commented Nov 11, 2017

@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 setup/start.sh stays focused on preparing clean mailserver solution.

@Memphizzz
Copy link

@Memphizzz Memphizzz commented Dec 8, 2017

@jirislav would you be able to replicate these changes on a 18.04 installation a few months from now? If so, wouldn't this be a good point to have MIAB switch to 18.04 as @JoshData suggested almost 2 years ago?

@jirislav
Copy link

@jirislav jirislav commented Dec 8, 2017

@Memphizzz I actually think it is already compatible with 18.04 :) .. I just have to try it out & fix problems that appear

@Memphizzz
Copy link

@Memphizzz Memphizzz commented Dec 8, 2017

@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.

@ppKrauss
Copy link

@ppKrauss ppKrauss commented Dec 27, 2017

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).

@ilyaevseev
Copy link

@ilyaevseev ilyaevseev commented Jan 2, 2018

Really???

Mail-in-a-Box only supports being installed on Ubuntu 14.04, sorry. You are running:

Ubuntu 16.04 LTS

We can't write scripts that run on every possible setup, sorry.
@jirislav
Copy link

@jirislav jirislav commented Jan 2, 2018

@ilyaevseev really what?

@cybercode
Copy link

@cybercode cybercode commented Jan 4, 2018

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?

@yodax
Copy link
Collaborator

@yodax yodax commented Jan 4, 2018

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.

@cybercode
Copy link

@cybercode cybercode commented Jan 4, 2018

@JoshData
Copy link
Member

@JoshData JoshData commented Jan 4, 2018

Folks, please open a new issue to talk about a new security issue.

@patricmutwiri
Copy link

@patricmutwiri patricmutwiri commented Jan 26, 2018

Do we have mail-in-a-box for ubuntu 16.04?

@Memphizzz
Copy link

@Memphizzz Memphizzz commented Jan 26, 2018

@patricmutwiri No, but as @jirislav pointed out, we might get a version for 18.04 once its released.

@patricmutwiri
Copy link

@patricmutwiri patricmutwiri commented Jan 26, 2018

Let me just head to iRedmail

@nikolay
Copy link

@nikolay nikolay commented Feb 15, 2018

There are a lot of 404s via apt-get update && apt-get upgrade. Any suggestion on the sources.list and sources.list.d contents?

@anoma
Copy link
Contributor

@anoma anoma commented Feb 19, 2018

No 404s here. Suggest you create a dedicated ticket unrelated to this one.

@JoshData
Copy link
Member

@JoshData JoshData commented Feb 25, 2018

Closing in favor of #1358.

@JoshData JoshData closed this Feb 25, 2018
@CHazz
Copy link

@CHazz CHazz commented Sep 21, 2018

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....

any news ? 14.04 is ,,, little retro :) maybe 20.04 ? no sorry bad joke ..

@mail-in-a-box mail-in-a-box locked as resolved and limited conversation to collaborators Sep 23, 2018
@JoshData
Copy link
Member

@JoshData JoshData commented Sep 23, 2018

See #1358.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet