Let's mark the whole /run/host hierarchy as something to ignore by PID 1 for generation of .mount units, i.e. consider it as "extrinsic". By unifying container mgr supplied resources in one dir it's also easy to exclude the whole lot from PID1's management inside the container. This is the right thing to do, since from the payload's PoV these mounts are just API and not manipulatable as they are established, managed and owned by the container manager, not the payload. (While we are it, also add the boot ID mount to the existing list, as nspawn and other container managers overmount that too, typically, and it is thus owned by the container manager and not the payload typically.)
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
