summaryrefslogtreecommitdiff
path: root/units/systemd-importd.service.in
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2015-02-24 17:23:53 +0100
committerLennart Poettering <lennart@poettering.net>2015-02-24 17:27:53 +0100
commit113b3fc1a8061f4a24dd0db74e9a3cd0083b2251 (patch)
tree603c98f39bdc563151446157e37400505f2b94ff /units/systemd-importd.service.in
parent15e80c7b75c3a3188bfaaa0baddccf31ae661a7a (diff)
importd: create a loopback btrfs file system for /var/lib/machines, if necessary
When manipulating container and VM images we need efficient and atomic directory snapshots and file copies, as well as disk quota. btrfs provides this, legacy file systems do not. Hence, implicitly create a loopback file system in /var/lib/machines.raw and mount it to /var/lib/machines, if that directory is not on btrfs anyway. This is done implicitly and transparently the first time the user invokes "machinectl import-xyz". This allows us to take benefit of btrfs features for container management without actually having the rest of the system use btrfs. The loopback is sized 500M initially. Patches to grow it dynamically are to follow.
Diffstat (limited to 'units/systemd-importd.service.in')
-rw-r--r--units/systemd-importd.service.in3
1 files changed, 0 insertions, 3 deletions
diff --git a/units/systemd-importd.service.in b/units/systemd-importd.service.in
index 26759ea0fb..a540040bfb 100644
--- a/units/systemd-importd.service.in
+++ b/units/systemd-importd.service.in
@@ -15,6 +15,3 @@ BusName=org.freedesktop.import1
CapabilityBoundingSet=CAP_CHOWN CAP_FOWNER CAP_FSETID CAP_MKNOD CAP_SETFCAP CAP_SYS_ADMIN CAP_SETPCAP
NoNewPrivileges=yes
WatchdogSec=1min
-PrivateTmp=yes
-ProtectSystem=full
-ProtectHome=yes