Run root isn't used for some directories

[scanon]

Feature request description

Even when specifying run root, some directories and files will still be created in XDG_RUNTIME_DIR. This makes it difficult to fully isolate podman instances. We are seeing issues with this when we run jobs in a batch system that does cleanup when a job ends. I'm not 100% but I think it is the some of the libpod state that is the main issue.

Suggest potential solution

It would be helpful if one could specify some additional flags and/or container.conf settings to force everything to use the run root location.

Have you considered any alternatives?

I have a workaround that creates symlinks in /run/user// for the various directories to isolate things, but it is a bit hacky.

Additional context

While this occurs in a batch computing environments, there may be other cases where this isolation would be useful.

[scanon]

@mheon Here is a write up of the issue we discussed. Let me know if you need more detail.

[Luap99]

Please specify the list of what files you are seeing being created under XDG_RUNTIME_DIR so we can better judge if that is expected or not.

The one think I am aware of is the netns path location but not sure about others.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[Luap99]

since there was no futher info here I am going to close this, the netns path is somewhat expected to be shared like that, at least as root anyway