Linux Container Development
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt-XAri/EZa3C4vJsYlp49lxw@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: containers and in-kernel nfs services
Date: Mon, 08 Feb 2010 17:28:22 +0300	[thread overview]
Message-ID: <4B701F86.1000905@msgid.tls.msk.ru> (raw)

Hello.

The question is how containers iteracts with in-kernel nfsd?

For example, I want to export a directory over nfs from one
container (with separate network and filesystem namespaces)
and mount it on another container on the same host.  Or on
entirely different machine, for that matter.  At the same
time, other containers and maybe the host itself may want
to export other filesystems, and since the same filesystem
may be visible in several containers, the result might be
that the same directory is exported multiple times by
different containers...

Is it ever possible/supported/feasible?

Thanks!

/mjt

                 reply	other threads:[~2010-02-08 14:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B701F86.1000905@msgid.tls.msk.ru \
    --to=mjt-xari/eza3c4vjsylp49lxw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox