chrisroberts
commented
11 years ago Hi @alff. The issue you are running into is with upstart. It uses inotify on /etc/init to reload the configuration files when they change. The overlayfs does not properly support inotify so upstart will fail to see the new conf file you dropped in. I'm actually starting to mess around with having vagabond provide alternatives via the Vagabondfile but it's still a little ways out.
Since you are running on precise, there's a good chance that aufs is still hanging around. You can attempt to use that instead, and if it's there, upstart will work as expected. Your Vagabondfile would look like this:
{
:nodes => {
:my_node => {
:template => 'ubuntu_1204',
:run_list => [],
:union => 'aufs'
}
}
}
alff
Hi Chris! I ran into the problem with Vagabond instalation on Ubuntu VM. How to reproduce my error: -create by kvm VM Ubuntu 12.04 LTS -install and setup Vagabond chef-server -up the new vagabond node (with same os: Ubuntu 12.04LTS) with empty run_list and ssh on it -according with this page (https://github.com/BrightcoveOS/Diamond/wiki/Installation) do this step: * apt-get install make pbuilder python-mock python-configobj python-support cdbs
After that if i'm trying to install diamond package (any version and/or builded on this node or on any other) this new service doesn't recognize as uptstart service (service: Unknown job: diamond). But if i build this package remotely and i install on Vagabond container only require packages (python-configobj and python-support) diamond package installs and works correctly. Any suggestions?