Exits if can't reach git repository on boot

[reynir]

This is likely due to git-kv, and maybe okay.

console 2025-10-28T00:59:18-00:00: 2025-10-28T00:59:18-00:00: [INFO] [tcpip-stack-direct] Dual TCP/IP stack assembled: [REDACTED]
console 2025-10-28T00:59:18-00:00: 2025-10-28T00:59:18-00:00: [INFO] [awa.client] negotiated: kex curve25519-sha256 host key alg rsa-sha2-256
console 2025-10-28T00:59:18-00:00: enc ctos chacha20-poly1305@openssh.com stoc chacha20-poly1305@openssh.com
console 2025-10-28T00:59:18-00:00: mac ctos none stoc none
console 2025-10-28T00:59:18-00:00: compression ctos none stoc none
console 2025-10-28T00:59:18-00:00: 2025-10-28T00:59:18-00:00: [WARNING] [awa.mirage] error Cannot parse point: invalid length while processing data
console 2025-10-28T00:59:18-00:00: 2025-10-28T00:59:18-00:00: [ERROR] [git-fetch] The Git peer is not reachable.
console 2025-10-28T00:59:18-00:00: 2025-10-28T00:59:18-00:00: [ERROR] [application] couldn't initialize git repository git@[REDACTED]:robur/ns-robur-coop.git#master: error fetching: No connection found
console 2025-10-28T00:59:18-00:00: Solo5: solo5_exit(64) called

[hannesm]

This is indeed related to git-kv, and a bit unclear to me whether it is good or not. On the one side, a typo in the git url should not lead to restart-looping -- on the other side, a (temporary) network failure should lead to restarting the unikernel.... I don't know what to do here.