Ubuntu 14.04, Digitalocean - VM kernel panic about zulip

[timabbott]

Which digitalocean machine type were you using? Could be you don't have enough memory.

[lfaraone]

It also looks like you're using VirtualBox inside an already-virtualized environment. Can you use the LXC provider for Vagrant instead?

[ccope]

Note that you'll also need to switch the vagrant box name in order to use LXC, if you go that route. use fgrehm/trusty64-lxc.

@lfaraone If a user has a dedicated ubuntu vm, could they just skip vagrant and use the provisioning script from the Vagrantfile?:

sudo git clone https://github.com/zulip/zulip.git /srv/zulip
sudo apt-get update
sudo apt-get install -y python-pbs
python /srv/zulip/provision.py

[timabbott]

Yes, that should work (we do basically that in the .travis.yml file)

[timabbott]

@ccope @lfaraone is the problem here that our "vagrant up" instructions should include "--provider=LXC" or something?

[lfaraone]

@timabbott:

our "vagrant up" instructions should include "--provider=LXC" or something?
Well, we'll fall back to VirtualBox if you didn't install vagrant-lxc-plugin.

@Cam:

If a user has a dedicated ubuntu vm, could they just skip vagrant and use the provisioning script from the Vagrantfile?:
Yes.

[ccope]

If you want to support LXC, you'll need to add a section to the vagrant configuration to override the box name.

config.vm.provider "lxc" do |lxc, override|
  override.vm.box = "fgrehm/trusty64-lxc"
end

[timabbott]

@ccope this is our Vagrantfile, which I think already does that: https://github.com/zulip/zulip/blob/master/Vagrantfile

[ccope]

Oh hey, whaddya know, I missed it. I'm used to Vagrantfiles defaulting to Virtualbox and having overrides for lxc, not the other way around.

[flashjames]

@ccope

config.vm.provider "lxc" do |lxc, override|
override.vm.box = "fgrehm/trusty64-lxc"
end

Solved it.

Here's how the file looks after edits.
https://www.dropbox.com/s/z3evf4jxbljpqoy/Screenshot%202015-10-01%2016.46.41.png?dl=0

"Which digitalocean machine type were you using? Could be you don't have enough memory."
Ubuntu box with 512 ram

[timabbott]

@jenso OK just FYI 512MB of RAM is lower than we recommend right now (see #32 for discussion of how we can improve this), so you may experience OOM issues if you try running a server with that little RAM in production.