Boot loop

[starman2k01]

[15:05:25] INFO: Initializing Gemini CLI environment...
/run.sh: line 134: GEMINI_API_KEY: unbound variable
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
s6-linux-init-shutdown: fatal: unable to talk to shutdownd: Operation not permitted
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[15:05:45] INFO: Initializing Gemini CLI environment...

[oded996]

Fixed in v2.4.20. The cause was a strict shell check on the GEMINI_API_KEY variable when it was not yet configured. The startup script now handles missing keys gracefully using standard shell defaults. Please update to the latest version to resolve the boot loop.

[oded996]

Resolved in v2.6.4. The unbound variable errors have been handled in the updated startup scripts.