can you paste the logs and the vagrant file?

the home should exists otherwise the machine wont work (as vagrant use the
vagrant user)

What I think it is, is the permissions... if you are mouting /home in the
vm, that usually will use root as user/password and vagrant wont have
permissions to cd into that.. that's why the chdir error.


Thats why I suggested use /home/user and not /home as a whole.. and mount
each /home/user with guid/uid

home is a particular directory in unix that require the user to own it..

I won't suggest mount /home as 777 as is waaay bad practice..

Alvaro.


On Sun, Apr 27, 2014 at 5:33 AM, Goodbytes <[email protected]> wrote:

> On boot, its basically just the OS trying to cd into the user directory,
> which should be /home/vagrant and currently doesn't exist, easily fixed by
> adding a vagrant dir... although would be much nicer if we could change the
> home directory for a user
>
> On Saturday, 26 April 2014 04:09:00 UTC+1, Alvaro Miranda Aguilera wrote:
>>
>>
>> On Fri, Apr 25, 2014 at 10:15 PM, Goodbytes <[email protected]> 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 that error?
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to