Date: Wed, 08 Aug 2012 14:57:08 -0400 From: Fbsd8 <fbsd8@a1poweruser.com> To: Adam Vande More <amvandemore@gmail.com> Cc: freebsd-questions@freebsd.org, blackfriar <blackfriar@inhio.eu> Subject: Re: NFS within a Jail?! Message-ID: <5022B684.7010803@a1poweruser.com> In-Reply-To: <CA%2BtpaK2sFU%2BjMf6f7Yir7o9JjKUK=u-p1syFONds0MV=M7nZqg@mail.gmail.com> References: <1344347348.23440.5.camel@blackfriar.inhio.eu> <5022715C.9010301@a1poweruser.com> <CA%2BtpaK2sFU%2BjMf6f7Yir7o9JjKUK=u-p1syFONds0MV=M7nZqg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam Vande More wrote: > On Wed, Aug 8, 2012 at 9:02 AM, Fbsd8 <fbsd8@a1poweruser.com> wrote: >> Long answer is; NFS requires rpcbind to function. rpcbind is dependent on >> a network stack. Jails do not have their own network stack, they use the >> hosts network stack. > > > Dealing with this has been SOP practice in jails since their inception. > See man 8 jail. The best way to run the NFS server is from the jail. > Running it host side is the hard part. > http://www.freebsd.org/cgi/query-pr.cgi?pr=133265 The jail code maintainer says NFS server/client will not work jailed. So since you say this is SOP (standard operation procedure) then why is there no documentation available on how to do it? All the Google hits for "NFS running from Freebsd jail" end with no one got it to work. Have you done this? Do you have a procedure to post or know of a posted procedure giving step-by-step sequence to get NFS running in a jail with or without VIMAGE/VNET for Release 8.x or 9.x versions? > >> There is some experimental software to give each jail its own network >> stack but I sure would not deploy a production system based on this. >> > > There are a number of people who have reached the > opposite decision concerning VIMAGE/VNET enabled jails. They are much > easier to work with and provide nice capabilities. > Still doesn't change the FACT it's experimental!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5022B684.7010803>