Add cloud-init and open-vm-tools

[fzdarsky]

Summary by CodeRabbit

• New Features
  • Integrated support for cloud instance initialization and enhanced virtual machine performance by installing cloud-init and open-vm-tools in container builds.
• Chores
  • Improved container maintenance by performing cleanup of package caches and logs after installation.

[coderabbitai]

Walkthrough

The changes update multiple Containerfiles for CentOS and Fedora on both amd64 and arm64 architectures. A new RUN command is introduced in each file to install the packages cloud-init and open-vm-tools, create a symbolic link for cloud-init.target in the systemd default target directory, clean up DNF caches and logs, and enable the vmtoolsd.service. The new command is inserted into the existing build sequence without altering other installation or cleanup operations, and no changes were made to exported or public entities.

Changes

File(s)	Change Summary
centos-bootc/…/Containerfile.{amd64,arm64}	Added a new RUN command that installs cloud-init and open-vm-tools, creates a symbolic link for cloud-init.target, cleans DNF cache/logs, and enables vmtoolsd.service. The command is placed after installing flightctl-agent and before podman-compose.
fedora-bootc/…/Containerfile.{amd64,arm64}	Introduced a RUN command to install cloud-init and open-vm-tools, create a symbolic link for cloud-init.target, clean up DNF cache/logs, and enable vmtoolsd.service. The command integrates seamlessly with the existing package installation and cleanup workflow.

Sequence Diagram(s)

sequenceDiagram
    participant Build as Docker Build Process
    participant DNF as Package Manager
    participant S as Systemd

    Build->>DNF: Install packages (cloud-init, open-vm-tools)
    DNF-->>Build: Installation complete
    Build->>S: Create symlink for cloud-init.target in default target
    S-->>Build: Symlink created
    Build->>DNF: Clean up DNF cache and logs
    DNF-->>Build: Cleanup complete
    Build->>S: Enable vmtoolsd.service
    S-->>Build: Service enabled

Loading

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 027ee4a and 640f23d.

📒 Files selected for processing (4)

• centos-bootc/bootc/Containerfile.amd64 (1 hunks)
• centos-bootc/bootc/Containerfile.arm64 (1 hunks)
• fedora-bootc/bootc/Containerfile.amd64 (1 hunks)
• fedora-bootc/bootc/Containerfile.arm64 (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: build-changed-bootc-images (centos-bootc) / build-bootc-images (ubuntu-24.04-arm)
• GitHub Check: build-changed-bootc-images (fedora-bootc) / build-bootc-images (ubuntu-24.04)
• GitHub Check: build-changed-bootc-images (centos-bootc) / build-bootc-images (ubuntu-24.04)
• GitHub Check: build-changed-bootc-images (fedora-bootc) / build-bootc-images (ubuntu-24.04-arm)

🔇 Additional comments (4)

centos-bootc/bootc/Containerfile.amd64 (1)

9-14: Appropriate addition of cloud-init and open-vm-tools

The addition of cloud-init and open-vm-tools is well-structured and follows the same pattern as other package installations in this file. The symbolic link ensures cloud-init runs at boot time, and enabling vmtoolsd.service is necessary for VMware guest operations. The cleanup operations maintain consistency with other similar blocks in the file.

fedora-bootc/bootc/Containerfile.amd64 (1)

17-22: Well-integrated cloud-init and open-vm-tools installation

The implementation maintains consistency with the CentOS counterpart and follows the established pattern in the file. The package installation, symbolic link creation, cleanup, and service enablement are correctly implemented.

centos-bootc/bootc/Containerfile.arm64 (1)

9-14: Consistent implementation across architectures

The changes mirror those in the amd64 version, maintaining consistency across architectures. Including open-vm-tools on ARM is forward-looking as VMware continues to expand ARM support.

fedora-bootc/bootc/Containerfile.arm64 (1)

17-22: Maintains consistency across distributions and architectures

The changes align with both the amd64 version and the CentOS counterparts, ensuring a uniform approach across all container variants. The implementation follows the established pattern of package installation, configuration, cleanup, and service enablement.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.