Vagrant is creating files and folders in my project

Posted by SERPRO on Server Fault See other posts from Server Fault or by SERPRO
Published on 2014-06-11T14:31:48Z Indexed on 2014/06/11 15:29 UTC
Read the original article Hit count: 263

Filed under:

puppet

|

vagrant

Recently I updated Vagrant (v 1.6.3) and I noticed that in the folder of my project there are some new folders and files like:

d20140610-11944-1j6n1cz/
d20140610-15421-1pkz3t8/
vagrant20140610-11944-p76ezc
vagrant20140610-11944-p76ezc2
vagrant20140610-11944-yt3bhz
vagrant20140610-11944-yt3bhz1
vagrant20140610-15421-mfqrig
vagrant20140610-15421-mfqrig1
vagrant20140610-15421-y3r71a
vagrant20140610-15421-y3r71a2
vagrant20140610-15421-y3r71a2.lock

most of the files are empty, others have text like this:

source "https://rubygems.org"
source "http://gems.hashicorp.com"
gem "vagrant", "= 1.6.3"
group :plugins do
gem "vagrant-login", nil, {}
gem "vagrant-share", nil, {}
end

The directories have a file named config with this this info:

BUNDLE_PATH: "/home/user/.vagrant.d/gems"

Is this some kind of debug option? how can I disable it?

© Server Fault or respective owner

Related posts about puppet

migrating puppet clients to a new puppet master (old puppet master server gone, only using backup)

as seen on Server Fault - Search for 'Server Fault'
My puppet master server had a hardware failure, and I have restored to another box. However this box has different hardware and hostname. If I restore the existing /etc/puppet directory to the new server, the puppetmaster will not start with the following error; # puppetmasterd --debug --verbose Could… >>> More
puppet rspec no such file to load -- rspec-puppet (LoadError)

as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
I have no prior experience at all of ruby. I am not interested in ruby (and so have no knowledge of rails etc) as such but am using puppet to manage a group of servers. I have written some modules and the rspec-puppet system looks like it would be very useful. However, I cannot get rspec-puppet… >>> More
Puppet: Making Windows Awesome Since 2011

as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
Originally posted on: http://geekswithblogs.net/robz/archive/2014/08/07/puppet-making-windows-awesome-since-2011.aspxPuppet was one of the first configuration management (CM) tools to support Windows, way back in 2011. It has the heaviest investment on Windows infrastructure with 1/3 of the platform… >>> More
What causes this logrotate behavior in Puppet?

as seen on Server Fault - Search for 'Server Fault'
After running logrotate, Puppet starts writing it's logs into /var/log/puppet/masterhttp.log-20130616. How come it doesn't keep logging in /var/log/puppet/masterhttp.log? It seems normal behavior is renaming the original log-file and start with a clean fresh log-file to start writing in that log… >>> More
solved: puppet master REST API returns 403 when running under passenger works when master runs from command line

as seen on Server Fault - Search for 'Server Fault'
I am using the standard auth.conf provided in puppet install for the puppet master which is running through passenger under Nginx. However for most of the catalog, files and certitifcate request I get a 403 response. ### Authenticated paths - these apply only when the client ### has a valid certificate… >>> More

Related posts about vagrant

Puppet Directory and File ownership ignored

as seen on Server Fault - Search for 'Server Fault'
Puppet seems to be lying to me, which is not very nice. I am trying to set some files and directories included in /vagrant/src to be 666 and 777, and set the ownership group to the correct Apache user (using the PuppetLabs Apache module). Output from Puppet says yes. [default] Running provisioner:… >>> More
"vagrant up" fails with "NS_ERROR_CALL_FAILED" error [on hold]

as seen on Server Fault - Search for 'Server Fault'
I am following the basic "Getting Started" guide: http://docs.vagrantup.com/v2/getting-started/index.html I ran vagrant init <etc> followed by vagrant up, but it fails with "NS_ERROR_CALL_FAILED" error. Then by enabling debug logging with VAGRANT_LOG=debug vagrant up, I get the following error… >>> More
vagrant and puppet security for ssl certificates

as seen on Server Fault - Search for 'Server Fault'
I'm pretty new to vagrant, would someone who knows more about it (and puppet) be able to explain how vagrant deals with the ssl certs needed when making vagrant testing machines that are processing the same node definition as the real production machines ? I run puppet in master / client mode, and… >>> More
Authenticate to VM using vagrant up

as seen on Super User - Search for 'Super User'
Authentication failure during Vagrant Up, while vagrant ssh and ssh vagrant@localhost -p2222 works I would like to execute a shell script using Vagrant at boot. Vagrant is unable to Authenticate, while the VM has been started using vagrant up: c:\temp\helloworld>vagrant up Bringing machine 'default'… >>> More
Vagrant ssh fails with VirtualBox

as seen on Super User - Search for 'Super User'
vagrant up fails when it gets to the ssh part: myterminal$ vagrant up [default] VM already created. Booting if its not already running... [default] Running any VM customizations... [default] Clearing any previously set forwarded ports... [default] Forwarding ports... [default] -- ssh: 22 => 2222… >>> More