diff options
| author | Lennart Poettering <lennart@poettering.net> | 2021-05-26 11:10:18 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2021-07-09 18:32:28 +0200 |
| commit | a645a25f1284904bd6ff80ff6f6e3f3602976236 (patch) | |
| tree | 1b8ebfc420d5b856a60a49a150e711300c8fd914 | |
| parent | 44cc44b3657217e67345c0486bee63366666a0d8 (diff) | |
| download | systemd-a645a25f1284904bd6ff80ff6f6e3f3602976236.tar.gz | |
man: try to clarify that nss-mymachines does not provide name resolution outside its own scope
Fixes: #18229
(cherry picked from commit 74c88a25203e7db293ca7a1c31b789e6558129fd)
| -rw-r--r-- | man/nss-mymachines.xml | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/man/nss-mymachines.xml b/man/nss-mymachines.xml index b2785df410..7ca9a58132 100644 --- a/man/nss-mymachines.xml +++ b/man/nss-mymachines.xml @@ -39,6 +39,15 @@ Note that the name that is resolved is the one registered with <command>systemd-machined</command>, which may be different than the hostname configured inside of the container.</para> + <para>Note that this NSS module only makes available names of the containers running immediately below + the current system context. It does not provide host name resolution for containers running side-by-side + with the invoking system context, or containers further up or down the container hierarchy. Or in other + words, on the host system it provides host name resolution for the containers running immediately below + the host environment. When used inside a container environment however, it will not be able to provide + name resolution for containers running on the host (as those are siblings and not children of the current + container environment), but instead only for nested containers running immediately below its own + container environment.</para> + <para>To activate the NSS module, add <literal>mymachines</literal> to the line starting with <literal>hosts:</literal> in <filename>/etc/nsswitch.conf</filename>.</para> |