Nick Labich
a9e860f22e
Prior to this change, no user shell can be specified in the user records passed into a container via --bind-user=. This new option allows users to: 1. When false (the default), continue to specify no user shell for each bound user record, resulting in the use of the container's default shell for bound users. 2. When true, include each host user's shell in the corresponding user record passed into a container (via --bind-user=). 3. When an absolute path, set that path as the user shell for each user record passed into a container (via --bind-user=). This does not change the existing behavior, but allows users to opt-in to either copy the shells specified by the host user records or override the shell explicitly by path.
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 Code Map for information about this repository's layout and content.
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, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS