Closed
Bug 1318199
Opened 9 years ago
Closed 8 years ago
Document that Vagrant doesn't support encrypted folders in the troubleshooting section
Categories
(Tree Management :: Treeherder, defect, P3)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: goma, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.90 Safari/537.36
Steps to reproduce:
I'm using Ubuntu 16.04 on my computer with the option for Encrypted folders.
After cloned the repo, when I type "vagrant up", It's getting an error.
Actual results:
I'm getting the following error:
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o 'vers=3,udp' 172.28.128.1:'/home/goma/Programming/OpenSourceProjects/treeherder' /home/vagrant/treeherder
Stdout from the command:
Stderr from the command:
stdin: is not a tty
mount.nfs: access denied by server while mounting 172.28.128.1:/home/goma/Programming/OpenSourceProjects/treeherder
Expected results:
It should mount the NFS partition.
It seems that NFS is incompatible with Encrypted folder.
http://serverfault.com/questions/200759/exportfs-warning-home-user-share-does-not-support-nfs-export
I think that it would be good to show this information in the Troubleshooting session, on the documentation
Comment 1•8 years ago
|
||
Hi!
The Vagrant docs mention this here:
https://www.vagrantup.com/docs/synced-folders/nfs.html#other-notes
...though it's understandable that people might not start looking in the vagrant docs straight away, so I wouldn't be against adding a note to the Treeherder setup troubleshooting docs.
Though we're hopefully going to move from Vagrant to Docker (bug 1169263), at which point I think I number of these papercuts will go away.
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Summary: Problems to set vagrant up with encrypted folders → Document that Vagrant doesn't support encrypted folders in the troubleshooting section
Comment 2•8 years ago
|
||
This issue hasn't come up since, and given it's documented in the Vagrant docs and we're hopefully going to move to Docker at some point this year anyway, let's not worry about this for now.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
| Assignee | ||
Updated•4 years ago
|
Component: Treeherder: Docs & Development → TreeHerder
You need to log in
before you can comment on or make changes to this bug.
Description
•