Public: anyone can read this; nobody can change it.
azure-gate: fix bicep deploy on the NixOS runner (PATH bicep) #151
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
Next failure after the clone/pager fixes — and the reason the last run failed in 7s. Pulled the actual error from Forgejo's action-log storage: az deployment group create -f main.bicep auto-downloads a generic-linux bicep ELF into /.azure/bin, and the vxrail runner is NixOS, which can't exec it.
shipped merged
Sign in to join this conversation.
new above
offline
Next failure after the clone/pager fixes — and the reason the last run failed in ~7s. Pulled the actual error from Forgejo's action-log storage:
az deployment group create -f main.bicepauto-downloads a generic-linuxbicepELF into~/.azure/bin, and the vxrail runner is NixOS, which can't exec it. The run got all the way through clone → SP login → RG create → deploy before dying here (and it tore down cleanly — no leak), so the earlier fixes are confirmed working.Fix: add
nixpkgs#bicepto the workflow'snix shell, and ingate.shsetaz config set bicep.use_binary_from_path=truewheneverbicepis on PATH. So CI uses the nix bicep; a laptop with no bicep on PATH keeps using az's own download (which works fine off-NixOS). Laptop == CI preserved.This should be the last blocker for a green vms run.
🤖 Generated with Claude Code