From 6cf5928ff1ee2f9d21662d74057f3a8331ddedfb Mon Sep 17 00:00:00 2001 From: Steven Dake Date: Sun, 8 Nov 2015 16:34:32 -0500 Subject: Base image changes for drop-root The reason we are doing drop root is so that a network exposed software component (i.e. glance) cannot be used to affect the immutability of the container which it runs in. I have tried several different approaches and this is the only approach which puts glance in PID=1 while ensuring no files may be written by the glance process in the container image except for the log files. Change-Id: Ifd3c8c361b78d0e4791dade3afa6435290407c41 Partially-Implements: blueprint drop-root --- docker/base/start.sh | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docker/base/start.sh') diff --git a/docker/base/start.sh b/docker/base/start.sh index bbe321a80..a39380f7e 100644 --- a/docker/base/start.sh +++ b/docker/base/start.sh @@ -1,8 +1,10 @@ #!/bin/bash set -o errexit -# Processing /opt/kolla/config_files/config.json -python /usr/local/bin/kolla_set_configs +# Processing /opt/kolla/config_files/config.json as root. This is necessary +# to permit certain files to be controlled by the root user which should +# not be writable by the dropped-privileged user, especially /run_command +sudo -E kolla_set_configs CMD=$(cat /run_command) ARGS="" -- cgit v1.2.3