-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
centos/7 box does not sync correctly between host and VM #9
Comments
@corylown did you install the |
@adjam I did try installing that. But I'll give it another try before proposing moving to a different box. |
According to CentOS/sig-cloud-instance-build@ab1d40d it seems that adding bzip2 to the image is what makes the difference. |
@adjam So, I think part of my confusion was that both /vagrant and ~/synced appear to show the same shared directory on the VM, but only ~/synced actually syncs content between the VM and the host. Closing the issue. |
It might make sense to resurrect this issue or create a new one to make the mount point more sensible, in that case. Vagrant tends to mount the directory containing the Vagrantfile as the home directory, but during development I wanted the home directory to be mostly empty, so Spofford can create directories there and they wouldn't have to go into .gitignore. In mounting . under ~/synced, though, it gets confusing. I'm open to suggestions. |
My understanding is that the standard mount point for the shared directory in the VM is /vagrant |
Which is of course correct. Never mind =) |
@adjam @queryluke I propose then that we remove the ~/synced directory (unless there is a reason it's needed that I don't know about) and just use the standard synced directory mount point of /vagrant. If that's OK with everyone I will update the Vagrantfile and references to the ~/synced dir in the setup and readme. |
I have no objections |
Use /vagrant as synced dir instead of ~/synced; Closes #9
I think I can fix this by using a different centos 7 box.
geerlingguy/centos7 is suggested in this thread:
CentOS/sig-cloud-instance-build#27
The text was updated successfully, but these errors were encountered: