container-entrypoint: add custom git path to safedirs

The git clone path can also be controlled with the GIT_CLONE_PATH
environment variable. While this is ignored by kas (as the clone
is executed in a cleaned environment), it can happen when cloning the
main repository (the one kas then is run from). As the GitLab CI passes
the environment variables directly to the container invocation, the
GitLab CI cloning of the main repository already uses them, which fails
if the path is not added to the safedirs.

We now account for this special case.

Signed-off-by: Felix Moessbauer <[email protected]>
Signed-off-by: Jan Kiszka <[email protected]>

Author: fmoessbauer

container-entrypoint

@@ -76,6 +76,11 @@ if [ -z "$USER_ID" ] && [ -n "$CI_PROJECT_DIR" ]; then
 	# with our builder user. We handle that internally in kas, but we
 	# need the exception here as well for git calls outside of kas.
 	sudo git config --system safe.directory "$CI_PROJECT_DIR"
+
+	# Account for externally specified git clone path
+	if [ -n "$GIT_CLONE_PATH" ]; then
+		sudo git config --system --add safe.directory "$GIT_CLONE_PATH"
+	fi
 fi
 if [ -z "$USER_ID" ] || [ "$USER_ID" = 0 ]; then
 	# Not a kas-container call, or we shall run everything as root