feat(fw): authorize ssh keys for root on cloonar.vms guests #164
No reviewers
Labels
No labels
bug
enhancement
in-progress
needs-info
needs-triage
p0
ready-for-agent
ready-for-human
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/nixos!164
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/qemu-vm-root-keys"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Authorizes the configured
cloudInit.sshKeysfor root on everycloonar.vms.<name>guest, sossh root@<ip>works with the normal key — which is what thenixos-infectbootstrap (ADR-0018, #161) expects.Why it didn't before: the cloud-init seed listed only the per-VM user (
dev/openclaw) underusers:, and the NoCloud seed provides no datasource keys, so root'sauthorized_keyswas never written (and Ubuntu cloud images disable root SSH by default).Change: add a
{ name = "root"; ssh_authorized_keys = sshKeys; }entry to the cloud-initusers:list and setdisable_root = false. The per-VM sudo user is unchanged, so openclaw's setup still runs asopenclaw.Scope: future provisions only — an already-provisioned guest (e.g. the running
dev-tempon .97.16) won't re-run cloud-init for the same instance-id, so usessh dev@…there.Pre-commit dry-build green for all 6 hosts. Note: eval can't exercise cloud-init — root login is verifiable only on the next fresh provision.