Skip to content

run-ephemeral: Use cloud-init=disabled instead of ds=None #379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cgwalters merged 1 commit into from
Sep 26, 2026
Merged

run-ephemeral: Use cloud-init=disabled instead of ds=None #379

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions crates/kit/src/run_ephemeral.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1696,10 +1696,16 @@ StandardOutput=file:/dev/virtio-ports/executestatus
kernel_cmdline.push("console=hvc0".to_string());
}
if cloudinit {
// We don't provide any cloud-init datasource right now,
// though in the future it would make sense to do so,
// and switch over our SSH key injection.
kernel_cmdline.push("ds=None".to_string());
// Fully disable cloud-init in ephemeral VMs. We don't provide any
// cloud-init datasource, and using `ds=None` (which tells cloud-init
// to use DataSourceNone) causes problems: the cloud-init generator
// still creates its activation symlink, which triggers a systemd
// drop-in condition (disable-sshd-keygen-if-cloud-init-active.conf)
// that prevents sshd-keygen from generating host keys. Since
// cloud-init itself never runs in the ephemeral VM (the boot target
// doesn't pull in multi-user.target), sshd ends up with no host
// keys and fails to start.
kernel_cmdline.push("cloud-init=disabled".to_string());
}

// Add Ignition platform kernel argument if Ignition config is specified
Expand Down
Loading