Re: Need advice about fixing PROC mount failures in a DIY Linux container

From	Lew Pitcher <lew.pitcher@digitalfreehold.ca>
Newsgroups	comp.os.linux.misc
Subject	Re: Need advice about fixing PROC mount failures in a DIY Linux container
Date	2023-01-07 18:17 +0000
Organization	A noiseless patient Spider
Message-ID	<tpccvo$3hj0v$3@dont-email.me> (permalink)
References	<tpahpv$3a27i$1@dont-email.me> <tpaker$3advh$1@dont-email.me> <k1tln0F7l9eU1@mid.individual.net>

Show all headers | View raw

On Sat, 07 Jan 2023 11:41:34 -0500, John-Paul Stewart wrote:

> [Followups set to comp.os.linux.misc since I don't read any of the other
> groups]
> 
> On 1/6/23 21:12, Lew Pitcher wrote:
>> 
>> The reason I get "Operation not permitted" on the
>> container /proc mount on my "production" system is that
>> I also run an nfs server on my "production" system (and
>> do not run one on my development system), and is nfs
>> server maintains two mountpoints within the /proc
>> filesystem.
>> 
>> Apparently, the attempt to mount /proc within my container
>> was blocked by the existance of these two mount points
>> (/proc/fs/nfs and /proc/fs/nfsd), as when I shut down my
>> rpc and nfs servers, and umounted these two mounts, I could
>> successfully run my demo container.
>> 
>> /Now/ the question is: how do I get my container /proc mount
>> to ignore or bypass these two nfsd mounts?
> 
> In your OP you showed that you've got MS_REC in the mountflags field,
> which will cause a recursive mount;  i.e., you've explicitly asked for
> the inclusion of the NFS-related subtrees.  Have you tried without that
> flag?  MS_BIND would seem a more appropriate choice instead, IMHO, since
> it doesn't do the recursion.  Then, by default, the subtrees will be
> excluded.

Well, I've now tried an MS_BIND mount for that new-root /proc filesystem,
and while the mount no longer returns an error, it seems to fail to mount
the procfs to my new-root /proc. At least, with busybox providing both
the local shell and utilities under this new-root environment,
"ls -l /proc" reports only the "." and ".." directories, and not the
expected proc filesystem directories.

So, onward to checking out the other mount options, and the propogation
effects there-of.

[snip]

Thanks again for the hint.
-- 
Lew Pitcher
"In Skills, We Trust"

Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Need advice about fixing PROC mount failures in a DIY Linux container Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-01-07 01:27 +0000
  Re: Need advice about fixing PROC mount failures in a DIY Linux container Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-01-07 02:12 +0000
    Re: Need advice about fixing PROC mount failures in a DIY Linux container Jasen Betts <usenet@revmaps.no-ip.org> - 2023-01-07 07:06 +0000
    Re: Need advice about fixing PROC mount failures in a DIY Linux container John-Paul Stewart <jpstewart@personalprojects.net> - 2023-01-07 11:41 -0500
      Re: Need advice about fixing PROC mount failures in a DIY Linux container Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-01-07 17:42 +0000
      Re: Need advice about fixing PROC mount failures in a DIY Linux container Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-01-07 18:17 +0000
    Re: Need advice about fixing PROC mount failures in a DIY Linux container Rainer Weikusat <rweikusat@talktalk.net> - 2023-01-09 19:27 +0000

csiph-web