Micka33 / Micka33/vagrant-sickrage

your machine doesn't support NFS (Ubuntu)

Open
#2 1 comment 0 reactions 1 assignee View on GitHub

@Micka33 is already working on this.

Since Aug 7, 2014.

help wanted
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

I'm using Ubuntu 14.04.1 LTS trusty.

➜  vagrant-sickrage git:(master) ✗ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:   trusty
➜  vagrant-sickrage git:(master) ✗ 

Upon vagrant up, I get the following error:

➜  vagrant-sickrage git:(master) ✗ vagrant up
Bringing machine 'coreos' up with 'virtualbox' provider...
==> coreos: Box 'coreos-alpha' could not be found. Attempting to find and install...
    coreos: Box Provider: virtualbox
    coreos: Box Version: >= 308.0.1
==> coreos: Loading metadata for box 'http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json'
    coreos: URL: http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vagrant.json
==> coreos: Adding box 'coreos-alpha' (v399.0.0) for provider: virtualbox
    coreos: Downloading: http://alpha.release.core-os.net/amd64-usr/399.0.0/coreos_production_vagrant.box
    coreos: Calculating and comparing box checksum...
==> coreos: Successfully added box 'coreos-alpha' (v399.0.0) for 'virtualbox'!
==> coreos: Importing base box 'coreos-alpha'...
==> coreos: Matching MAC address for NAT networking...
==> coreos: Checking if box 'coreos-alpha' is up to date...
==> coreos: Setting the name of the VM: vagrant-sickrage_coreos_1327409530983_66532
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.

How to fix it ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.