X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=fef5c2c83a8151336b4069b5ed4f7e9873496f25;hp=cf6756952466bc561f22ed692652ab5f82002c9d;hb=df688b23daff9382b8fa2609cfcf73315a3b896e;hpb=25f5971b5e0b3ab5b91a7d0359cd7f5a5094c1d0 diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index cf6756952..fef5c2c83 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -114,6 +114,11 @@ two containers is complete and the containers will share very few runtime objects except for the underlying file system. + + systemd-nspawn implements the + Container + Interface specification. @@ -183,7 +188,7 @@ Makes the container appear in - other hierarchies that the name=systemd:/ one. + other hierarchies than the name=systemd:/ one. Takes a comma-separated list of controllers. @@ -198,6 +203,85 @@ loopback device. + + + + Mount the root file + system read only for the + container. + + + + + + List one or more + additional capabilities to grant the + container. Takes a comma separated + list of capability names, see + capabilities7 + for more information. Note that the + following capabilities will be + granted in any way: CAP_CHOWN, + CAP_DAC_OVERRIDE, CAP_DAC_READ_SEARCH, + CAP_FOWNER, CAP_FSETID, CAP_IPC_OWNER, + CAP_KILL, CAP_LEASE, + CAP_LINUX_IMMUTABLE, + CAP_NET_BIND_SERVICE, + CAP_NET_BROADCAST, CAP_NET_RAW, + CAP_SETGID, CAP_SETFCAP, CAP_SETPCAP, + CAP_SETUID, CAP_SYS_ADMIN, + CAP_SYS_CHROOT, CAP_SYS_NICE, + CAP_SYS_PTRACE, CAP_SYS_TTY_CONFIG, + CAP_SYS_RESOURCE, CAP_SYS_BOOT. + + + + + + Control whether the + container's journal shall be made + visible to the host system. If enabled + allows viewing the container's journal + files from the host (but not vice + versa). Takes one of + no, + host, + guest, + auto. If + no, the journal is + not linked. If host, + the journal files are stored on the + host file system (beneath + /var/log/journal/<machine-id>) + and the subdirectory is bind-mounted + into the container at the same + location. If guest, + the journal files are stored on the + guest file system (beneath + /var/log/journal/<machine-id>) + and the subdirectory is symlinked into the host + at the same location. If + auto (the default), + and the right subdirectory of + /var/log/journal + exists, it will be bind mounted + into the container. If the + subdirectory doesn't exist, no + linking is performed. Effectively, + booting a container once with + guest or + host will link the + journal persistently if further on + the default of auto + is used. + + + + + + Equivalent to + . +