Wrap Anaconda

Aperta
#74 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
linux, rust
Ambito
cli

Direzione di ricerca

The issue names crates/kit/src/libvirt/anaconda.rs, crates/kit/src/libvirt/mod.rs, and crates/kit/src/main.rs as implementation entry points. Start by reading existing bcvk libvirt commands and DomainBuilder virtiofs support, then investigate the referenced Fedora bare-metal bootc guide and osbuild/rhinstaller issues and PRs. Done means a working Anaconda installation workflow, but the issue describes a broad spike and multi-stage implementation without tests or a narrow first task.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

We should add something like bcvk libvirt anaconada-install quay.io/myimage that would wrap and automate https://docs.fedoraproject.org/en-US/bootc/bare-metal/ - especially in terms of using the same --bind-storage-ro that we use for to-disk so that we can directly do an install from the host containers-storage:.

Support Anaconda-as-container

I think a first key deliverable from this is a spike on converting the ISO to a bootc container image (or better - always generating the ISO from a bootc container image). Then we can always use bcvk ephemeral to launch it the same way we do with a basic bcvk to-disk!

Gather information by looking at issues and PRs especially comments @cgwalters in the https://github.com/osbuild and https://github.com/rhinstaller/ orgs

Wrap w/libvirt

Then once we have the core infrastructure the next key bit is something like this:

bcvk libvirt anaconda-install --kickstart=/path/to/my.ks quay.io/myimage

## Implementation Plan: `bcvk libvirt anaconda`

This command will streamline Anaconda-based bootc installation by automating the workflow from https://docs.fedoraproject.org/en-US/bootc/bare-metal/.

Command Signature
bcvk libvirt anaconda <CONTAINER_IMAGE> [OPTIONS]

Arguments & Options

- <CONTAINER_IMAGE>: Bootc container image to install (required)
- --kickstart <PATH>: Custom kickstart file (optional, generates basic one if not provided)
- --remote-image: Skip virtiofs setup, have Anaconda fetch image from registry
- --anaconda-version <N>: Fedora version for installer (default: auto-detect from /etc/os-release)
- --disk-size <SIZE>: Installation disk size (default: 20G)
- --memory <SIZE>: VM memory allocation (default: 10G - Anaconda needs more than typical VMs)
- --name <NAME>: Domain name (default: auto-generate from image)
- --ssh-port <PORT>: SSH port forward (default: 10022)

Architecture Overview

1. Fetch Anaconda Installer (OCI Artifact)

Building on https://fedoraproject.org/wiki/Changes/KickstartOciArtifacts:

# Fetch from quay.io/fedora/fedora-anaconda-artifacts:N-arch
skopeo copy docker://quay.io/fedora/fedora-anaconda-artifacts:42-x86_64 dir:/tmp/anaconda

Extract required files:
- vmlinuz - Anaconda kernel
- initrd.img - Anaconda initramfs
- install.img - Anaconda stage2 squashfs

Future enhancement: Use podman artifact when available (not yet in Podman as of Nov 2025)

2. Virtiofs Setup (unless --remote-image)

Use libvirt's built-in virtiofs support - libvirt handles virtiofsd spawning and lifecycle:

let virtiofs_fs = VirtiofsFilesystem {
    source_dir: container_storage_path.to_string(),
    tag: "hoststorage".to_string(),
    readonly: true,
};

domain_builder = domain_builder.with_virtiofs_filesystem(virtiofs_fs);

This leverages existing DomainBuilder infrastructure that already handles:
- Automatic virtiofsd process management
- Proper permission handling via libvirt
- Socket cleanup on domain shutdown

3. Kickstart Generation/Extension

Auto-generate or extend user kickstart with virtiofs magic:

%pre section (added only if not --remote-image):
# Mount tmpfs for fast container operations
mkdir -p /var/lib/containers
mount -t tmpfs -o size=10485760k tmpfs /var/lib/containers

# Mount virtiofs host storage
mkdir -p /run/virtiofs-mnt-hoststorage
mount -t virtiofs hoststorage /run/virtiofs-mnt-hoststorage

# Configure containers storage.conf
cat > /etc/containers/storage.conf << 'EOF'
[storage]
driver = "overlay"

[storage.options]
additionalimagestores = [
  "/run/virtiofs-mnt-hoststorage"
]
EOF

bootc install command:
# With virtiofs:
bootc install to-filesystem --source-imgref=containers-storage:localhost/<image> --stateroot=default

# With --remote-image:
bootc install to-filesystem --source-imgref=<registry-image> --stateroot=default

4. Libvirt Domain Creation

Create transient domain with:
- Direct kernel boot: -kernel vmlinuz -initrd kickstart-initrd.cpio.gz
  - Kernel cmdline: inst.ks=file:///kickstart.ks inst.sshd
  - Kickstart injected via custom initrd overlay
- Virtiofs filesystem (if enabled): Handled by libvirt
- Virtio serial ports for log streaming:
  - /dev/virtio-ports/org.fedoraproject.anaconda.log.0 → anaconda-install.log
  - /dev/virtio-ports/org.fedoraproject.anaconda.program.0 → anaconda-program.log
- SSH access: Port forward for debugging (default 10022)
- Storage: Installation disk + install.img attachment

5. Post-Installation (Future Enhancement)

Optional flags to handle the resulting disk:
- --import-domain: Import installed disk as new libvirt domain
- --boot-test: Boot the installed system to verify it works

Implementation Files

- crates/kit/src/libvirt/anaconda.rs - Main implementation
- crates/kit/src/libvirt/mod.rs - Add Anaconda subcommand variant
- crates/kit/src/main.rs - Wire up dispatch

Key Differences from anaconda-bootc-scripts

1. Virtiofs via libvirt: Use DomainBuilder::with_virtiofs_filesystem() instead of manual podman unshare + virtiofsd spawning
2. Integrated workflow: Single command vs. multiple scripts
3. Transient domains: Leverages libvirt for lifecycle management
4. Auto-detection: Automatically detect Fedora version and arch

Testing

# Build local test image
podman build -t localhost/my-bootc-test .

# Run installation
bcvk libvirt anaconda localhost/my-bootc-test

# With custom kickstart
bcvk libvirt anaconda localhost/my-bootc-test --kickstart my.ks

# Remote image (no virtiofs)
bcvk libvirt anaconda quay.io/myimage --remote-image

Follow-up Enhancements

1. Support podman artifact when available
2. Progress reporting with real-time log display
3. Auto-import installed disk as libvirt domain
4. Boot testing of installed system
5. Support for other architectures (aarch64)
6. Caching of Anaconda artifacts
</details>
Lingua principale
Rust
Stelle
142
Fork
40
Merge medio
2g 22h
PR unite (30g)
10

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bootc-dev/bcvk

Tutte le issue di bootc-dev/bcvk

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.