From 191be1b2cf45c166c9228a122c84dde2db393e1f Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Wed, 3 Jun 2026 09:54:21 -0700 Subject: [PATCH] teslamate: keep Erlang release cookie (removeCookie = false) The Nix mixRelease strips releases/COOKIE by default and expects RELEASE_COOKIE at runtime, but teslamate's start script reads the file and crash-loops without it. teslamate is single-node (no distributed Erlang exposed beyond :4000), so keeping the build-generated cookie in the release is the simplest self-contained fix. Co-Authored-By: Claude Opus 4.8 (1M context) --- containers/teslamate/default.nix | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/containers/teslamate/default.nix b/containers/teslamate/default.nix index 024aa6f..e126561 100644 --- a/containers/teslamate/default.nix +++ b/containers/teslamate/default.nix @@ -46,6 +46,12 @@ let pname = "teslamate"; inherit version src elixir; + # Keep the build-generated Erlang cookie in the release. mixRelease + # strips it by default (expecting RELEASE_COOKIE at runtime), but the + # start script reads releases/COOKIE. teslamate is single-node (no + # distributed Erlang exposed), so a baked-in cookie is fine. + removeCookie = false; + mixFodDeps = beamPackages.fetchMixDeps { pname = "mix-deps-teslamate"; inherit src version elixir;