-
Notifications
You must be signed in to change notification settings - Fork 181
Troubleshooting
In order to find out more about what's going on under the hood on vagrant, prepend VAGRANT_LOG=debug to your vagrant commands. For lxc-starts debugging set LXC_START_LOG_FILE:
LXC_START_LOG_FILE=/tmp/lxc-start.log VAGRANT_LOG=debug vagrant up
This will output A LOT of information on your terminal and some useful information about lxc-start to /tmp/lxc-start.log.
It happened to me quite a few times in the past and it seems that it is related to a bug on linux kernel, so make sure you are using a bug-free kernel (>= 3.5.0-17.28). More information can be found on:
- https://bugzilla.kernel.org/show_bug.cgi?id=47181
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021471
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065434
Sometimes the dev boxes I'm using are not able to lxc-start containers anymore. Most of the times it was an issue with the arguments I provided to it for customization or the buggy kernel. If you run into that, rollback your changes and try to vagrant reload the dev box. If it still doesn't work, please file a bug at the issue tracker.