Here’s the relevant script snippet for d4m clone and setup (adjust as neccessary).
- if [[ "$OS_PLATFORM" == 'Darwin' ]]
- export D4M="$WORKDIR/docker/df4-nfs"
- export D4M_CONF="$D4M/etc/d4m-nfs-mounts.txt"
the d4m-nfs fully supports relative paths from docker-compose now so everythin is serverd over nfs - no changes to what you do now - it shou;ld be a native replacement
👍 we us e a shell script - it clones d4m-nfs, configures it and runs it then starts up container via docker-compose.
the NFS mounts make virtual folder mounts really really fast …. visibly noticeable compared to native xhyve-osx disk layer (really noticable)
We are slowly moving to Linux as the dev env for this reason
yeah - we are now hitting the hurdle of minor behaviour differences between container on Mac and container on Linux ….
Our front-end guys run webpack local outside container but the front-end HTML is served through the container so recompile speed is native …
With this mount file it becomes a drop-in replacement for the native mount system (but is faster). Need to remove the docker mounts in docker for mac before running the d4m-nfs shel;l script to start it all up. Existing docker files don’t require changes
Yup it is awesome. using Docker for Mac native right now (about to switch to linux for other reasons). It just works - esp. now. 3 months ago it was a lot more work to get going
For people using Docker on Mac OSX and hating speed of virtual folder mounts. Get on the NFS train at … https://github.com/IFSight/d4m-nfs