fix(cloud): fedora docker install and debian 9p cloud-init error

[NovusEdge]

Two cloud-provisioning fixes found by booting each distro locally on QEMU/KVM.

fedora docker (24a2883)

dnf config-manager --add-repo was removed in dnf5 (Fedora 41+). install-fedora.sh aborted under set -e with Unknown argument "--add-repo", so docker-ce never installed and docker.service did not exist. Write the repo file straight into /etc/yum.repos.d/ with curl; that works on dnf4 and dnf5.

debian 9p cloud-init error (0f0665f)

debian's cloud kernel (deb13-cloud) ships no 9p module. The seed still added a work 9p mount, so cloud-init's mounts module failed with unknown filesystem type '9p' and reported the whole seed as errored on every boot. nofail did not help: it covers a missing device, not an unknown filesystem type. Skip the mount for debian only. alpine, ubuntu, fedora, and arch all load 9p.

Verification (local QEMU/KVM)

• fedora-cloud 44: before Unit docker.service could not be found; after docker daemon running, version 29.7.2.
• debian-13: cloud-init status now done, was error; no 9p entry in fstab.
• debian docker, arch docker: both came up at 29.7.2 on the same pass.
• ubuntu, fedora, arch: 9p module loads, /mnt/work mounts, so their mounts document stays.

[coderabbitai]

Warning

Review limit reached

@NovusEdge, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 83 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 20116f54-548a-4f64-9507-f2525218f46d

📥 Commits

Reviewing files that changed from the base of the PR and between 2b8cfae and 0f0665f.

📒 Files selected for processing (3)

• internal/cloudinit/cloudinit.go
• internal/cloudinit/cloudinit_test.go
• internal/recipes/bundled/docker/install-fedora.sh

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}