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 and for redir debugging use REDIR_LOG:

REDIR_LOG=1 LXC_START_LOG_FILE=/tmp/lxc-start.log VAGRANT_LOG=debug vagrant up

This will output A LOT of Vagrant debugging information on your terminal, lxc-start stuff to /tmp/lxc-start.log and redir related output to /var/log/syslog.

I'm unable to restart containers!

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.

I'm using Eclipse to launch vagrant-lxc containers and I'm getting a "There was an error executing ["sudo", "lxc-version"]"

See #88 for more information

Can't install software on containers!

This seems to be related to some iptables rules declared on hosts, see #94 for more information

Can't use ufw on guest containers

There seems to be an issue with Kernel module loading on vagrant-lxc boxes. See #104 and this message on lxc-users mailing list for more information