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

Use watcher on virtualbox synced folders #26

Closed
julienkosinski opened this issue Aug 2, 2017 · 11 comments
Closed

Use watcher on virtualbox synced folders #26

julienkosinski opened this issue Aug 2, 2017 · 11 comments

Comments

@julienkosinski
Copy link

julienkosinski commented Aug 2, 2017

Hello,

@radovskyb Thank you very much for the great software!

I use Vagrant over Virtualbox with synced folder of type Virtualbox.
My host system is Windows 10 Creator's Update, my guest system is Ubuntu 16.04 with Go 1.8.3.
As described, watcher does not work with synced folders on Virtualbox if I trigger an event from the host OS in the synchronized folder while running watcher in the guest OS.

Is that logical? What should I do to workaround this?

Thank you! :)

@radovskyb
Copy link
Owner

Hey @julienkosinski, sorry for the late reply!

I'm not too sure I can help with this one as I'm unfamiliar with using Vagrant and don't really use Virtualbox much either so not sure how they are meant to interact with each other etc.

I'll leave this issue opened if you like and maybe someone with experience can help you.

@julienkosinski
Copy link
Author

julienkosinski commented Aug 7, 2017

Thank you very much for your reply. :-) I hope I'll find the solution for this but I don't know where to search...

@jeevatkm
Copy link

@radovskyb @julienkosinski I have verified this scenario.

My host machine Mac OS and vagrant VM of ubuntu. Watcher is able to detect the changes within VM and also host machine changes.

I don't have Windows OS host machine, so I'm unable to verify that. I have only Windows OS guest VM for aah framework testing purpose.

@julienkosinski
Copy link
Author

Thank you very much for your help!

I'm running with the latest virtual box guest addition 5.1.26. Files and folder are synced correctly but no events are triggered, I can reproduce this on another computer with the same configuration as host, Windows Creator's Update.
I suppose this could be a bug in Virtualbox but I'll investigate a bit later on this :).

@julienkosinski
Copy link
Author

julienkosinski commented Aug 12, 2017

@radovskyb @jeevatkm
Unfortunatly I did some research and it seems that this problem is related to virtualbox and filesystem. There's a known bug avoiding such events (at least with nodejs) to work accross different filesystem.
https://www.virtualbox.org/ticket/10660

@jeevatkm What is strange though is that it is working on your side on MACOS. Do you have any Ext driver on your MAC?

@jeevatkm
Copy link

@julienkosinski I don't have any specific drivers. All I did was configuring config.vm.synced_folder in Vagrantfile and fired aah run. It's working at my end.

Please Note: watcher library doesn't use native filesystem events.

@julienkosinski
Copy link
Author

julienkosinski commented Aug 12, 2017

@jeevatkm Thank you for your response, as you said, because watcher isn't relying on filesystem events then, it could be other thing.

@radovskyb
Copy link
Owner

Hey @jeevatkm, @julienkosinski,

Sorry a little late to the convo here. @jeevatkm, thanks for helping out with this issue.

@julienkosinski, it might be worth trying out fsnotify and seeing how you go with it if you haven't already given it a try, since that does use filesystem events.

@julienkosinski
Copy link
Author

julienkosinski commented Aug 30, 2017

Hi @radovskyb, @jeevatkm!

Sorry for the delay...

I have news! :D
All events from synced folder are seen as WRITE events. The reason why I did not see this sooner is that I used the basic test in the example which by default is limited to MOVE and RENAME events.

@radovskyb
Copy link
Owner

Hey @julienkosinski,

Glad to hear that you worked it out!

I probably should have asked to see the code from the beginning, but at least I'll remember if someone else comes along with the same question :P

I'll close this issue then since it sounds to me like it's been resolved :)

@julienkosinski
Copy link
Author

@radovskyb Sorry, I forgot to response. Yeah, that's just some events which are not available in this configuration but I suppose that's normal. Thanks for your help! :D

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