Skip to content
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

Closed
corylown opened this issue Dec 20, 2016 · 9 comments
Closed

centos/7 box does not sync correctly between host and VM #9

corylown opened this issue Dec 20, 2016 · 9 comments
Assignees

Comments

@corylown
Copy link
Contributor

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

@corylown corylown self-assigned this Dec 20, 2016
@adjam
Copy link
Collaborator

adjam commented Dec 20, 2016

@corylown did you install the vagrant-vbguest vagrant plugin? I'm not otherwise opposed to using a different box.

@corylown
Copy link
Contributor Author

@adjam I did try installing that. But I'll give it another try before proposing moving to a different box.

@adjam
Copy link
Collaborator

adjam commented Dec 20, 2016

According to CentOS/sig-cloud-instance-build@ab1d40d it seems that adding bzip2 to the image is what makes the difference.

@corylown
Copy link
Contributor Author

@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.

@adjam
Copy link
Collaborator

adjam commented Dec 22, 2016

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.

@corylown
Copy link
Contributor Author

My understanding is that the standard mount point for the shared directory in the VM is /vagrant

@adjam
Copy link
Collaborator

adjam commented Dec 22, 2016

Which is of course correct. Never mind =)

@corylown
Copy link
Contributor Author

@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.

@corylown corylown reopened this Dec 22, 2016
@queryluke
Copy link
Collaborator

I have no objections

@adjam adjam closed this as completed in 3170c10 Jan 3, 2017
adjam added a commit that referenced this issue Jan 3, 2017
Use /vagrant as synced dir instead of ~/synced; Closes #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants