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

native_osx does not work with docker-machine vbox / fusion #346

Closed
EugenMayer opened this issue May 5, 2017 · 8 comments
Closed

native_osx does not work with docker-machine vbox / fusion #346

EugenMayer opened this issue May 5, 2017 · 8 comments

Comments

@EugenMayer
Copy link
Owner

@EugenMayer EugenMayer commented May 5, 2017

I seems like vboxfs does not trigger fsevents on the receiving end, making it a bad companion for the unison watcher, since no inotify events are triggered.

I do not think we can do anything about this.

docker-machine + fusion does work though

@EugenMayer
Copy link
Owner Author

@EugenMayer EugenMayer commented May 5, 2017

seems not even work with fusion right now. Container -> host works, but host -> container does not. I will need to look into this

@EugenMayer EugenMayer changed the title native_osx does not work with vboxfs native_osx does not work with docker-machine vbox / fusion May 5, 2017
@EugenMayer
Copy link
Owner Author

@EugenMayer EugenMayer commented May 5, 2017

Seems to be in fact a deal breaker - https://groups.google.com/forum/#!topic/vagrant-up/ZZpM1nTCSSQ both, vmware fusion and virtualbox do not implement file system events

@mike-potter
Copy link

@mike-potter mike-potter commented May 5, 2017

Yeah, I think something else is wrong. I also just tried it with docker-machine + xhyve and it also didn't work.

@greggilbert
Copy link
Contributor

@greggilbert greggilbert commented May 5, 2017

Just jumping in. Docker 4 Mac, OSX 10.12.4. Tried 0.4.1 with native_osx, and while all the containers came up and unison was running in the sync containers, it wasn't actually syncing.

@EugenMayer
Copy link
Owner Author

@EugenMayer EugenMayer commented May 5, 2017

@mike-potter it does work with docker for mac, since they use osxfs - which xhyve on docker machine does not use.

That said, i corrected the strategie guide to reflect the docker-machine issue
@greggilbert please open a different issue

EugenMayer added a commit that referenced this issue May 5, 2017
@EugenMayer
Copy link
Owner Author

@EugenMayer EugenMayer commented May 5, 2017

Thats known for a very long time already, not sure how i missed that: https://groups.google.com/forum/#!topic/vagrant-up/ZZpM1nTCSSQ

@infostreams
Copy link
Contributor

@infostreams infostreams commented Apr 9, 2020

You can work around this issue and get the native_osx strategy working by making a change to the options in your docker-stack.yaml, like this:

version: "2"
options:
  native_osx_image: 'infostreams/docker-sync-unison'

syncs:
  code_sync:
    sync_strategy: 'native_osx'
    src: '/my/path/to/my/code'
    sync_excludes: ['node_modules', 'vendor']
    sync_args: "-copyonconflict"

If you add the native_osx_image key as described above, it will run a background program inside the docker-sync container to trigger the missing filesystem events. More info here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants