From d20c2a767e7f4cc053b983ca35c504db9f294065 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dirk=20M=C3=BCller?= <dirk@dmllr.de>
Date: Mon, 2 Dec 2024 12:54:16 +0100
Subject: [PATCH] Disable protected-mode in valkey

upstream does this by recompiling valkey which is not something
that we can easily do. let's see how far we'll get by patching
the configuration file.
---
 src/bci_build/package/valkey.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/bci_build/package/valkey.py b/src/bci_build/package/valkey.py
index 01a54f2ee..e301599df 100644
--- a/src/bci_build/package/valkey.py
+++ b/src/bci_build/package/valkey.py
@@ -39,8 +39,9 @@
             )
         ],
         license="BSD-3-Clause",
-        package_list=["valkey"],
+        package_list=["valkey", "sed"],
         entrypoint=["/usr/bin/valkey-server"],
+        cmd=["/etc/valkey/valkey.conf"],
         entrypoint_user="valkey",
         exposes_ports=[TCP(6379)],
         volumes=["/data"],
@@ -49,6 +50,7 @@
         ),
         custom_end=textwrap.dedent(
             f"""
+            {DOCKERFILE_RUN} sed -e 's/^protected-mode yes/protected-mode no/' -e 's/^bind .*//' < /etc/valkey/default.conf.example > /etc/valkey/valkey.conf
             {DOCKERFILE_RUN} install -o valkey -g valkey -m 750 -d /data
             WORKDIR /data
         """