summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2017-02-16 14:38:05 +0100
committerLennart Poettering <lennart@poettering.net>2017-02-17 11:47:20 +0100
commitaa10469e17bd145c5d5c8c9b93438a0ee74d1ecf (patch)
tree3e803986d57d6aff4b973dfa4e0ef9ad187c84b1 /man
parent7f43928ba6258c66296614dd46ff7600e0e47b5f (diff)
man: document that user namespacing complicates file copies
Diffstat (limited to 'man')
-rw-r--r--man/systemd-nspawn.xml7
1 files changed, 6 insertions, 1 deletions
diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml
index 17c14e9f22..96f8c3a61f 100644
--- a/man/systemd-nspawn.xml
+++ b/man/systemd-nspawn.xml
@@ -474,7 +474,12 @@
<para>Note that the picked UID/GID range is not written to <filename>/etc/passwd</filename> or
<filename>/etc/group</filename>. In fact, the allocation of the range is not stored persistently anywhere,
- except in the file ownership of the files and directories of the container.</para></listitem>
+ except in the file ownership of the files and directories of the container.</para>
+
+ <para>Note that when user namespacing is used file ownership on disk reflects this, and all of the container's
+ files and directories are owned by the container's effective user and group IDs. This means that copying files
+ from and to the container image requires correction of the numeric UID/GID values, according to the UID/GID
+ shift applied.</para></listitem>
</varlistentry>
<varlistentry>