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

mounting {ip}:/Users on /Users failed: Bad file descriptor #64

Closed
bennypowers opened this issue Oct 20, 2016 · 6 comments
Closed

mounting {ip}:/Users on /Users failed: Bad file descriptor #64

bennypowers opened this issue Oct 20, 2016 · 6 comments

Comments

@bennypowers
Copy link

docker-machine 0.8.1
el cap

begin
  curl -s https://raw.githubusercontent.com/adlogix/docker-machine-nfs/master/docker-machine-nfs.sh |  sudo tee /usr/local/bin/docker-machine-nfs > /dev/null
  sudo chmod +x /usr/local/bin/docker-machine-nfs
  docker-machine rm dev
  docker-machine create -d virtualbox dev
  docker-machine-nfs dev --nfs-config="-alldirs -maproot=0"
end 

👇👇👇

Cannot detect the NFS mount :(

🙁🙁🙁

docker-machine ssh dev sudo mount -t nfs -o noacl,async 192.168.99.1:/Users /Users
mount: 192.168.99.1:/Users failed, reason given by server: Permission denied
mount: mounting 192.168.99.1:/Users on /Users failed: Bad file descriptor
@ellisio
Copy link

ellisio commented Oct 20, 2016

This is happening for me as well.

  • macOS Sierra
  • Docker Machine 0.8.2
  • Docker 1.12.2
  • VirtualBox 5.1.8 r111374

Installed via the Homebrew method. Ran docker-machine-nfs default, nothing fancy.

@ellisio
Copy link

ellisio commented Oct 20, 2016

PR #65 submitted for this issue. In the mean time, edit line 357 and remove the -network flag. This will fix /etc/exports and initialize NFS correctly on macOS.

@ahansson89
Copy link

Worked for me on

macOS Sierra
Docker Machine 0.8.2
Docker 1.12.2
VirtualBox 5.1.8 r111374

@tonivdv
Copy link
Member

tonivdv commented Oct 21, 2016

That's interesting. I don't have any issues on my setup ...

macOs Sierra
Docker Machine 0.8.2
Docker 1.12.2
VirtualBox 5.1.6 r110634

What do you get when running nfsd checkexports ?

@tonivdv
Copy link
Member

tonivdv commented Oct 21, 2016

On second thought, I do have the issue now ... But it does work for the ip-range. So the -network flag should only be used when the ip-range config is being used

@bennypowers
Copy link
Author

confirmed fix thanks

tonivdv added a commit that referenced this issue Oct 21, 2016
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

4 participants