On Tue, Nov 07, 2023 at 10:15:05AM +0800, Ian Kent wrote: > On 7/11/23 01:05, Robert Vasek wrote: > > Dear autofs community, > > > > We run an instance of the automount daemon inside a container (a part > > of a storage plugin in Kubernetes). The autofs mount root is shared > > between different containers, and must survive restarting the daemon. > > That sounds unusual, please tell me more about how this works? > > My thought was always that there are two ways one would use autofs in > a container. > > One is mapping an indirect mount root (from the init mount namespace) > as a volume into the container thereby using the daemon present in the init > namespace. Yes, this has had an expire problem for a long time but that will > change (soon I hope). > > The second way is to run an instance of the daemon completely independently > within the container. > > But this sounds like a combination of both of these which is something I > hadn't considered. FYI, as a third option/way, one thing we do is that we bind the root of direct automount maps into containers (though we're using singularity) and the automount bits continue to work just fine inside and out of said containers. We have not noticed any big issues with expirations not happening, at least that we can contribute specifically to the container use in these cases. Note that singularity seems to understand autofs mount points though, and if started with debug it walks and loads the direct map into its internal /proc/mounts, which is probably why it works so well. Now that I think of it, I have no idea if it continues to work with any paths added after the container starts though since it wouldn't have been there when starting and might not be seen as a trigger. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com
