Comment 23 for bug 1611444

@Dave

"In regards to interfaces I'm having difficulty finding any information on the 'interfaces.SecurityMount' interface."

This is an interface backend and something the interfaces themselves might use. This is an implementation detail of snapd and not something a developer needs to worry about. Though if curious, you can look at the code in snapd.git/interfaces/*.

(skipping the question David answered)

"Also please could you explain how in the future I'll be able to create a network namespace in one SNAP and put network interfaces into it (I know how to do this bit, we do it today) and then ACCESS these network interfaces from another SNAP. This will of course involve creating a process inside that second SNAP inside the designated network namespace. This is something we'll absolutely need to to do."

You are right that using a shared mount namespace per-snap does not directly help with sharing namespaces between snaps. The implementation for fixing this bug should be forward looking for when we want to design interfaces for sharing mount namespaces between snaps. Once we have the implementation for sharing mount namespaces robustly, we should have all the knowledge needed to design and implement support for sharing mount namespaces between snaps.