-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Ubuntu 14.04, Digitalocean - VM kernel panic #51
Comments
Which digitalocean machine type were you using? Could be you don't have enough memory. |
It also looks like you're using VirtualBox inside an already-virtualized environment. Can you use the LXC provider for Vagrant instead? |
Note that you'll also need to switch the vagrant box name in order to use LXC, if you go that route. use @lfaraone If a user has a dedicated ubuntu vm, could they just skip vagrant and use the provisioning script from the Vagrantfile?:
|
Yes, that should work (we do basically that in the .travis.yml file) |
@Cam:
|
If you want to support LXC, you'll need to add a section to the vagrant configuration to override the box name.
|
@ccope this is our Vagrantfile, which I think already does that: https://github.com/zulip/zulip/blob/master/Vagrantfile |
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. |
config.vm.provider "lxc" do |lxc, override| Solved it. Here's how the file looks after edits. "Which digitalocean machine type were you using? Could be you don't have enough memory." |
Running on
prox@test:~/zulip$ lsb_release -d
Description: Ubuntu 14.04.3 LTS
How it looks in terminal - https://www.dropbox.com/s/0ezckuzslxj6pxm/Screenshot%202015-09-27%2013.53.13.png?dl=0
How it looks in virtualbox - https://www.dropbox.com/s/93u22czp9ncehmu/Screenshot%202015-09-27%2013.53.53.png?dl=0
prox@test:~/zulip$ vagrant ssh -- -L9991:localhost:9991
VM must be running to open SSH connection. Run
vagrant up
to start the virtual machine.
The text was updated successfully, but these errors were encountered: