Public: anyone can read this; nobody can change it.

azure-gate: fix bicep deploy on the NixOS runner (PATH bicep) #151

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

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.

Notes

shipped merged

opened this view on origin

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:

The configuration value of bicep.use_binary_from_path has been set to 'false'.
Could not start dynamically linked executable: .../.azure/bin/bicep
NixOS cannot run dynamically linked executables intended for generic linux environments

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. 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#bicep to the workflow's nix shell, and in gate.sh set az config set bicep.use_binary_from_path=true whenever bicep is 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

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs