From 9c8832b5a78c4f8408b6d88e17e6f34c7cdd67b7 Mon Sep 17 00:00:00 2001
From: Valentin Lab <valentin.lab@kalysto.org>
Date: Fri, 17 May 2019 22:34:58 +0200
Subject: [PATCH] fix: [letsencrypt] scheduled call to compose would fail

Because it was requiring ``COMPOSE_LAUNCHER_OPTS`` to be set in the
cron file.
---
 letsencrypt/hooks/schedule_command-relation-joined | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/letsencrypt/hooks/schedule_command-relation-joined b/letsencrypt/hooks/schedule_command-relation-joined
index e22f8ee6..ddbd0e40 100755
--- a/letsencrypt/hooks/schedule_command-relation-joined
+++ b/letsencrypt/hooks/schedule_command-relation-joined
@@ -25,6 +25,8 @@ fi
 ## Warning: 'docker -v' will use HOST directory even if launched from
 ##   'cron' container.
 file_put "$DST" <<EOF
+COMPOSE_LAUNCHER_OPTS=$COMPOSE_LAUNCHER_OPTS
+
 $schedule     root  lock $label -D -p 10 -c "\
     compose crt $SERVICE_NAME renew" 2>&1 | ts '\%F \%T \%Z' >> $LOCAL_LOG