From b26f7f0169da2e956f85409eeea188fdf63d6830 Mon Sep 17 00:00:00 2001 From: Kevin Veen-Birkenbach Date: Thu, 21 May 2026 04:19:25 +0200 Subject: [PATCH] fix(compose): expose INFINITO_CONTAINER_NO_CA to the infinito container MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Same KeyError class as 28e7c20cf (INFINITO_SERVICES_DISABLED): roles/sys-svc-container/files/container.py:450 reads os.environ["INFINITO_CONTAINER_NO_CA"] strictly. The variable is emitted into the host shell .env via passthrough.STATIC_KEYS, but the compose `environment:` block did not forward it, so docker compose substitution was never wired into the container. Triggers as soon as the DinD-DNS handler (sys-svc-container/handlers) invokes `container run` from inside test-dns.sh, well past the first visible failure point. With this entry the inner container.py reads "" (the env/default.env default) and treats CA injection as enabled — the intended behaviour. Co-Authored-By: Claude Opus 4.7 (1M context) --- compose.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/compose.yml b/compose.yml index e9c4db0942..28df653835 100644 --- a/compose.yml +++ b/compose.yml @@ -73,6 +73,7 @@ services: - letsencrypt:/etc/letsencrypt/ environment: + INFINITO_CONTAINER_NO_CA: ${INFINITO_CONTAINER_NO_CA} INFINITO_DNS_IP: ${INFINITO_DNS_IP} INFINITO_DOMAIN: ${INFINITO_DOMAIN} INFINITO_IP4: ${INFINITO_IP4}