From e715af158d37bd9cccfdd36f4d3570cbce598479 Mon Sep 17 00:00:00 2001 From: Wild Dragon Dev Date: Thu, 4 Jun 2026 00:58:51 +0000 Subject: [PATCH] fix(node-agent): pass FRAMECACHE_IP to node-agent env --- docker-compose.worker.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docker-compose.worker.yml b/docker-compose.worker.yml index cf7d4b3..8d411e9 100644 --- a/docker-compose.worker.yml +++ b/docker-compose.worker.yml @@ -62,6 +62,7 @@ services: LIVE_DIR: ${LIVE_DIR:-/mnt/NVME/MAM/wild-dragon-live} # Framecache service URL (on the wild-dragon-worker network) FC_URL: ${FC_URL:-http://framecache:7435} + FRAMECACHE_IP: ${FRAMECACHE_IP:-172.18.91.223} # IP of the framecache host # net_ingest binary — runs inside the framecache container via docker exec. # node-agent has docker.sock so it can exec into the framecache container. # Override with a host-installed path if preferred. @@ -74,9 +75,9 @@ services: volumes: - /var/run/docker.sock:/var/run/docker.sock - /dev:/dev:ro - - /usr/local/bin/decklink-bridge:/usr/local/bin/decklink-bridge:ro - /mnt/NVME/MAM/wild-dragon-live:/mnt/NVME/MAM/wild-dragon-live:ro # Capture-driver deployment ("Capture Drivers / SDKs" in the Cluster admin + # Capture-driver deployment ("Capture Drivers / SDKs" in the Cluster admin # screen): the agent itself does NOT run dkms/modprobe — it spawns a # separate privileged ubuntu container that bind-mounts these host paths. # The agent only needs to *see* the repo path so it can pass it through as