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

Bug: NFS #1

Open
Metamogul opened this issue May 7, 2018 · 0 comments
Open

Bug: NFS #1

Metamogul opened this issue May 7, 2018 · 0 comments

Comments

@Metamogul
Copy link

Metamogul commented May 7, 2018

What I do:
$ vagrant up

What I expect
Vagrant starting and provisioning the Odoo VM.

What happens
The command fails with an error, output below.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'fedora/26-cloud-base' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 20170705
==> default: Loading metadata for box 'fedora/26-cloud-base'
    default: URL: https://vagrantcloud.com/fedora/26-cloud-base
==> default: Adding box 'fedora/26-cloud-base' (v20170705) for provider: virtualbox
    default: Downloading: https://vagrantcloud.com/fedora/boxes/26-cloud-base/versions/20170705/providers/virtualbox.box
==> default: Successfully added box 'fedora/26-cloud-base' (v20170705) for 'virtualbox'!
==> default: Importing base box 'fedora/26-cloud-base'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'fedora/26-cloud-base' is up to date...
==> default: Setting the name of the VM: odoo-vagrant_default_1525693890338_321
It appears your machine doesn't support NFS, or there is not an
adapter to enable NFS on this machine for Vagrant. Please verify
that `nfsd` is installed on your machine, and try again. If you're
on Windows, NFS isn't supported. If the problem persists, please
contact Vagrant support.

What I did to fix it
On my machine (Ubuntu 16.04) I needed to install NFS support with sudo apt install nfs-kernel-server nfs-common. After doing the error didn't occur anymore.

Thanks for you work anyway! Just right now I don't have the time for adding that to a readme and issuing a pull request - maybe you can add it sometime to the README.md

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

1 participant