summaryrefslogtreecommitdiff
path: root/test/TEST-13-NSPAWN-SMOKE/test.sh
diff options
context:
space:
mode:
authorSergiusz Urbaniak <sergiusz.urbaniak@gmail.com>2016-10-14 14:00:15 +0200
committerSergiusz Urbaniak <sergiusz.urbaniak@gmail.com>2016-11-18 09:50:40 +0100
commit4f086aab52812472a24c9b8b627589880a38696e (patch)
tree22fd04bdbb8346cbfda4201627eabf57c5b9ce51 /test/TEST-13-NSPAWN-SMOKE/test.sh
parent843d5baf6aad6c53fc00ea8d95d83209a4f92de1 (diff)
downloadsystemd-4f086aab52812472a24c9b8b627589880a38696e.tar.gz
nspawn: R/W support for /sys, and /proc/sys
This commit adds the possibility to leave /sys, and /proc/sys read-write. It introduces a new (undocumented) env var SYSTEMD_NSPAWN_API_VFS_WRITABLE to enable this feature. If set to "yes", /sys, and /proc/sys will be read-write. If set to "no", /sys, and /proc/sys will be read-only. If set to "network" /proc/sys/net will be read-write. This is useful in use-cases, where systemd-nspawn is used in an external network namespace. This adds the possibility to start privileged containers which need more control over settings in the /proc, and /sys filesystem. This is also a follow-up on the discussion from https://github.com/systemd/systemd/pull/4018#r76971862 where an introduction of a simple env var to enable R/W support for those directories was already discussed.
Diffstat (limited to 'test/TEST-13-NSPAWN-SMOKE/test.sh')
0 files changed, 0 insertions, 0 deletions