Bug 1199563 - mount in a different namespace
Summary: mount in a different namespace
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: fuse
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On: 1199554
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-06 15:57 UTC by hchen
Modified: 2018-04-02 14:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-02 14:16:08 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1199554 0 unspecified CLOSED Mount in different namespaces. 2023-09-14 02:55:47 UTC

Description hchen 2015-03-06 15:57:07 UTC
Description of problem:

Currently we have a problem with executing mount from one namespace to affect a different namespace.

The use case we are working towards is to allow a container application like gluster/cephs/nfs-utils to be run within a container in its own namespace.  Then allow the mount command to mount file systems in the hosts (primary) mnt namespaces.  

We would like to see a command like

mount --namespace=/proc/$n/ns/mnt

The critical point here is that the mount command would have to load all of its libraries and potentially helper routines before switching namespace.

An implementation of calling setns(2) in util-linux can be found at 
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-February/msg00064.html

A validation of calling setns(2) in mount.glusterfs  can be found in the prototype at https://github.com/rootfs/install-glusterfs-on-fc21/. The test description can be found in the README.md file.

Version-Release number of selected component (if applicable):


How reproducible:

NA

Steps to Reproduce:
1.
2.
3.

Actual results:

NA
Expected results:
NA

Additional info:

Comment 4 Amar Tumballi 2018-04-02 14:16:08 UTC
We now have CNS done for any container workloads, and there is no current focus on fixing this issue. Please reopen the bug if CNS (Container Native Storage doesn't solve the issue for you.


Note You need to log in before you can comment on or make changes to this bug.