path: root/doc/forum/Systemd_container_pre-setup_properties.mdwn
diff options
authorandrew2016-06-16 04:07:25 +0000
committeradmin2016-06-16 04:07:25 +0000
commit94e7eb26f7e0749dbc7ea17c75a6a4838d271b2e (patch)
treeb77225755872526373f1294adea1391de177bb39 /doc/forum/Systemd_container_pre-setup_properties.mdwn
parented37e6100e052180eca7883bde1dacee3cb5bf30 (diff)
Diffstat (limited to 'doc/forum/Systemd_container_pre-setup_properties.mdwn')
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Systemd_container_pre-setup_properties.mdwn b/doc/forum/Systemd_container_pre-setup_properties.mdwn
new file mode 100644
index 00000000..1cb94d66
--- /dev/null
+++ b/doc/forum/Systemd_container_pre-setup_properties.mdwn
@@ -0,0 +1,3 @@
+When creating a systemd container, what would be the best way to execute properties before propellor is run inside the container proper?
+I'm trying to setup packages for networking in a systemd container, but I first need the network to get the packages. Ideally, we should be able to run a few properties on the chroot that are used when creating a systemd container (and therefore use the host network). So far, I've solved this by adding the properties in the Systemd.Core.installed property. Not nice, but works if all your systemd containers are the same. I've tried creating a chroot myself, tar it and pass that to Systemd.container, but things got a little complicated. It also requires additional properties on the host that have to be moved if the container moved to another host.