Side-effects of running podman in different mount namespaces?

[tarun360]

Hello,

We need to run rootless podman commands (on a single machine) within different mount namespaces. We noticed that this causes podman to create new user & mount namespace corresponding to each mount namespace in which the command was executed.

This slightly deviates from the need of each podman command to be run in a single user & mount namespace, as mentioned in this red-hat article:

The pause process's role is to keep the user namespace alive, as all rootless containers must be run in the same user namespace. If they are not, some things (like sharing the network namespace from another container) would be impossible.

Our use case requires using --network=host, so the above limitation wouldn't effect us. Likewise, we don't require containers to join each other's container namespace, uts namespace etc. since we rely on host for such purposes. However, I wanted to ask if there are more limitations or side-effects which I should be aware of?

(This question is related to #19726)

Thanks,
Tarun

[tarun360]

Could someone take a look please? Maybe @Luap99 , since he answered a similar question of mine before. Thanks!!