Re: [vagrant-up] win8.1 - Lokale Domain nicht mehr aufrufbar!

Hi Alvaro, That was my first test but its the same behavior. :( The only thing that I have did was to install a Grunt environment with the following shell commands: npm install -g grunt-cli npm install grunt-contrib-clean grunt-contrib-less grunt-contrib-copy grunt-contrib-compress

Re: [vagrant-up] Correctly setting with the working path (CentOS)

hello, for the first issue, it's permissions, by default the permissions won't be very user friendly.. in the host, create one dir per user, and mount that as the /home/user if the user is already created check the documentation and use the user group if the user is not created, use gid/uid

Re: [vagrant-up] win8.1 - Lokale Domain nicht mehr aufrufbar!

sounds something local to the guest. Can you paste the output of these commands? iptables -L netstat -anp | grep ':port' not sure if it's port :80 or :443 at the guest, it could be firewall (iptables) or the webserver is not listening on the ip.. I am thinkig one of those 2 scenarios are

Re: [vagrant-up] 1.5.1 on windows 7 enterprise: runtime: panic before malloc heap initialized

Hi! This solves the problem here too, I don't know any other solution at the moment. I hope that somebody of vagrant pay attention to this, as we can not use new features and fixes of newer versions of this. Is there a way to open a bug for this? Kind regards Torsten Am Mittwoch, 23.

Re: [vagrant-up] Correctly setting with the working path (CentOS)

Thanks for the tip, i looked up the sed command and came up with this little beast: sudo rm -rf /var/www sudo ln -fs /home /var/www sudo sed -i 's@var/www/html@home@' /etc/httpd/conf/httpd.conf Just left with Could not chdir to home directory /home/vagrant: No such file or directory error but

[vagrant-up] Centos 6.5 Network Manager breaks vagrant ssh

I had an issue where i used a base vagrant box - https://dl.dropboxusercontent.com/s/np39xdpw05wfmv4/centos-6.5-x86_64.box which is an excellent one with puppet installed etc... - thanks to Edwin Beimond - he's a genius for sure. I wanted to add a decent desktop and chose gnome, via yum -y

[vagrant-up] Re: After adding Desktop to Centos 6.5 - vagrant ssh fails

Alvaro, worked it out myself ;-) I should have looked for your reply thanks On Friday, 18 April 2014 12:36:18 UTC+10, Michael Quinn wrote: All after adding Desktop (yum -y groupinstalll Desktop) and then restarting the VirtualBox image (vagrant up) I get the following

Re: [vagrant-up] I am confused about public keys and vagrant...

Vagrant deals with pre-built boxes/images, and under systems like Virtualbox VMWare, there is no mechanism for dropping a key into an image (under AWS digital ocean, they use the cloud-init/user-data hooks for dropping data into booting instances), for this reason, Vagrant defaults to using a

[vagrant-up] Vagrant + Grub Prompt

My vagrant up is not working anymore, which was working perfectly When I did *VBoxManage startvm ${MACHINE_ID}* I get the grub prompt and I am not sure what needs to be done to make it working as it was before.

[vagrant-up] Vagrant Persistent changes in box

I'm confused about how vagrant manages this.. suppose i start a box from a Vagrantfile ubuntu - vagrant up - vagrant ssh - inside the box - apt-get update apt-get install X packages - modify some config files after a while my host system reboots (for any reason), then i start the vagrant

[vagrant-up] Rsync on Windows

Hi. For some reason my last didn't post, so trying again... I'm very new to Vagrant and I am no sys admin. I'm hoping to use it to develop WordPress sites. I am currently using Chris Wiegman's Primary Vagrant https://github.com/ChrisWiegman/Primary-Vagrant which is working very well. Except

[vagrant-up] Vagrant with rsync on Windows

I'm very new to Vagrant but I've got it running using Chris Wiegman's Primary Vagrant to build WordPress websites. I am running Windows 8 64 bit and the guest OS is Ubuntu. As soon as I start to add lots of files, the site gets unbearably slow. I am assuming this is due to synced folders being

Re: [vagrant-up] I am confused about public keys and vagrant...

Thanks! At least that tells me I am not missing something obvious. I of course can set up an ansible script to do exactly this. However, it is just a bit ironic to have to do this on a system which is all about automating bringing up an experimental box to play in :) I would think there could

Re: [vagrant-up] Vagrant persistent changes in the box

i havent seen that my self, but there is other user reporting the same can you test other ubuntu image? On Sat, Apr 26, 2014 at 4:44 AM, Marcos Cano mc...@stsa.info wrote: im a little bit confused about how this is manage... maybe this is part of the intended way of working of Vagrant. i

Re: [vagrant-up] Vagrant + Grub Prompt

that means the boot process in the guest is not working. What stop you to do vagrant destroy and vagrant up to get a new working box? On Sat, Apr 26, 2014 at 6:00 AM, Kishore Kumar Vaishnav kishorevaish...@gmail.com wrote: My vagrant up is not working anymore, which was working perfectly

Re: [vagrant-up] Correctly setting with the working path (CentOS)

On Fri, Apr 25, 2014 at 10:15 PM, Goodbytes for...@gmail.com wrote: Could not chdir to home directory /home/vagrant: No such file or directory when that error happen? If there is at boot? when machine start? or after the machine boots, say one of the scripts? can you paste where you see