Project

General

Profile

Bug #28578

Add Configuring Persistent NFS-Shared Volumes section to Guide

Added by Corvin Wimmer over 1 year ago. Updated 4 months ago.

Status:
Done
Priority:
No priority
Assignee:
Timothy Moore II
Category:
Documentation
Target version:
Seen in:
Severity:
Low
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Specifically, containers using stack scoped volumes are unable to start using rancher-nfs (NFS pass-thru).

Please see here for more details and several problem reports of other FreeNAS users:
https://github.com/rancher/rancher/issues/7334

Unfortunately this makes it impossible to run many of the most popular containers on Docker Hub with NFS pass-thru.

History

#1 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to Marcelo Araujo
  • Target version set to 11.2-RC2

#2 Updated by Nick Wolff about 1 year ago

  • Category changed from OS to Documentation
  • Assignee changed from Marcelo Araujo to Release Council
  • Severity set to Low

This is more documentation/nfs specific then vm specific so I'm reassigning to release council to see if it makes sense to have doc's work someone skilled in NFS to figure out if there is a config recommendation to document to help resolve this.

#3 Updated by Dru Lavigne about 1 year ago

  • Assignee changed from Release Council to Warren Block
  • Target version changed from 11.2-RC2 to 11.2-U2

#4 Updated by Warren Block 6 months ago

  • Status changed from Not Started to Unscreened
  • Assignee changed from Warren Block to Timothy Moore II

#5 Updated by Timothy Moore II 6 months ago

  • Status changed from Unscreened to Not Started

After reading through the linked thread, here is the proposed docs change:

Add notes to Virtual Machines/Docker Hosts/Installing and Configuring the Rancher Server (16.5.5) describing a few configuration changes to get NFS pass-thru working with FreeNAS & RancherOS VM:

1. Configure the RancherOS VM to have these settings:

/nfs [ip](rw,sync,no_root_squash,no_subtree_check)

2. Configure the FreeNAS system with these settings: 1) In the NFS service settings set Enable 2) NFSv4 Enable NFSv3 ownership model for NFSv4
3) When mounting a volume, pass in the nocopy option, e.g. volume:/mnt/volume:nocopy

Please review and comment if this doesn't look correct. I'll link the PR here when it is opened.

#6 Updated by Timothy Moore II 6 months ago

WIP Docs PR: https://github.com/freenas/freenas-docs/pull/525. Reviews are welcome and needed.

#7 Updated by Timothy Moore II 6 months ago

  • Status changed from Not Started to In Progress

#8 Updated by Timothy Moore II 6 months ago

  • Status changed from In Progress to Blocked
  • Reason for Blocked set to Waiting for feedback

We need some feedback before the changes can be merged:

- What is the use case for these instructions? Every Rancher setup using multiple containers, or is there a specific configuration of Rancher, FreeNAS, and containers where this applies?

- Rancher documentation states "A NFS server has to be installed prior to launching the Rancher NFS driver." (https://rancher.com/docs/rancher/v1.6/en/rancher-services/storage-service/rancher-nfs/). Can the FreeNAS system or the Rancher VM function as this server or does it have to be a separate system?

Thanks!

#9 Updated by Timothy Moore II 5 months ago

Port of accepted docs changes to master branch: https://github.com/freenas/freenas-docs/pull/577

#10 Updated by Dru Lavigne 5 months ago

  • Subject changed from Rancher containers fail using NFS pass-thru to Add Configuring Persistent NFS-Shared Volumes section to Guide
  • Status changed from Blocked to Ready for Testing
  • Reason for Blocked deleted (Waiting for feedback)
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#15 Updated by Dru Lavigne 4 months ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF