Comments (7)
Hi Sebastian!
Could you please do the following:
- Clear exports file
- Run your Vagrant project with nfs mount, so it will create exports entry
- Post contents of exports file here
I want to see vagrants configuration, but don't have it installed
from docker-machine-nfs.
Hey @sebas5384 ,
Do you know what the default ip vagrant is using? Because exports conflict can happen without vagrant too if you use multiple docker-machine boxes. The thing with docker-machine is that it doesn't lock the ip address to a box (see docker/machine#1709). So it could be that when you start vagrant and later machine (and vice-versa) the ip changes constantly.
What I do to prevent this is following work around (docker/machine#1709 (comment)).
Try this and let us know.
That being all said, the management of the /etc/export in docker-machine-nfs is very basic, so it can be improved to avoid such things. But for for our (Adlogix/Adsdaq) needs it's not high priority.
Cheers
from docker-machine-nfs.
@krasilich and @tonivdv thanks your quick response!!
@krasilich here's my /etc/exports file when I have my vagrant's projects running.
$ cat /etc/exports
# VAGRANT-BEGIN: 501 6991d57f-1e23-42a1-a13a-d14d18659ec0
"/Users/sebas/Virtual/projects/myprojectwithvagrant" 192.168.22.11 -alldirs -mapall=501:20
# VAGRANT-END: 501 6991d57f-1e23-42a1-a13a-d14d18659ec0
@tonivdv I'll try to do that and I'll let you know.
Again thanks.
from docker-machine-nfs.
I tried to create a new machine with different CIDR, "192.168.98.1/24" instead of "192.168.22.1/24" like my vagrant's projects do:
$ docker-machine create -d virtualbox --virtualbox-hostonly-cidr "192.168.98.1/24" default98
$ docker-machine start default98
(default98) Starting VM...
Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
$ eval "$(docker-machine env default98)"
$ docker-machine-nfs default98
[INFO] Configuration:
- Machine Name: default98
- Shared Folder: /Users
- Force: false
[INFO] machine presence ... OK
[INFO] machine running ... OK
[INFO] Lookup mandatory properties ... OK
- Machine IP: 192.168.98.100
- Network ID: vboxnet8
- NFSHost IP: 192.168.98.1
[INFO] Configure NFS ...
!!! Sudo will be necessary for editing /etc/exports !!!
Password:
exports:5: /Users conflicts with existing export /Users/sebas/Virtual/projects/myprojectwithvagrant
exports:6: /Users conflicts with existing export /Users/sebas/Virtual/projects/myprojectwithvagrant
but still same error, maybe I'm doing something wrong :/
from docker-machine-nfs.
Hey @sebas5384 ,
I could be wrong but it could be related to the fact that one machine tries to share /Users/sebas/Virtual/... and the other /Users only. I would have to test this to confirm.
from docker-machine-nfs.
@tonivdv yep! that was the problem :(
So now I just comment the Vagrant mount whenever I want to use the docker-machine with nfs.
I can't figure it out which project should deal with this, but I feel like Vagrant isn't removing the Vagrant mount when the virtual machine is down. That could resolve this issue, ... I think.
Thanks for the help!
from docker-machine-nfs.
It's Local that should be using a more specific path, their path overlaps everything.
from docker-machine-nfs.
Related Issues (20)
- macOS Catalina HOT 17
- Cannot detect the NFS mount HOT 8
- How to specify uid / gid in /etc/exports
- checkMachineRunning invalid filter
- Are some still using this? HOT 1
- mounting {ip}:/Users on /Users failed: Bad file descriptor HOT 6
- Adding mount with similar machine name causes error HOT 3
- Support for Docker for Mac HOT 3
- So frustrated with docker for mac HOT 1
- Bug with 10 or more virtualbox network adapters HOT 1
- VMWare Fusion problems on macOS 10.12 HOT 1
- Not working with Parallels 12 Pro on Sierra HOT 3
- /usr/local/bin/docker-machine-nfs: 130: /usr/local/bin/docker-machine-nfs: Syntax error: "(" unexpected (expecting "}") HOT 2
- <3 HOT 1
- Stale file handle HOT 4
- Change document root
- Not syncing files properly in High Sierra HOT 21
- grep is not working HOT 4
- NFS mount fails with boot2docker v18.09.0 HOT 10
- Support docker-machine-driver-vmware and use machine ip for route
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker-machine-nfs.