install: Support /usr/lib/bootc/install-to-disk executable
- Lingua principale
- Rust
- Stelle
- 2.3k
- Fork
- 230
- Merge medio
- 3g 12h
- PR unite (30g)
- 38
Descrizione
One thing to consider: Support the container image to shipping its own default `to-disk` installer that sets up partitioning etc. that is an executable in `/usr/lib/bootc/install-to-disk` for example.
This would be clearer actually if we more cleanly severed the existing "to-disk" and "to-filesystem" code here, and we ship the `to-disk` setup as `/usr/lib/bootc/install-to-disk.default` or something?
Also xref https://github.com/containers/bootc/issues/437 where I think we need configurability for what the base image supports in general.
---
Alternatively to this, what I think could work well is just recommending that folks add their own `bootc install` wrapper in the container image e.g. `/usr/bin/exampleos-installer` that sets up partitioning using whatever CLI and configfiles it wants, then just invokes `bootc install to-filesystem`. Then they can also drop in a config file that disables `bootc install to-disk` entirely.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by reviewing the existing `bootc install to-disk` and `bootc install to-filesystem` behavior, then compare the alternatives described here: supporting `/usr/lib/bootc/install-to-disk` or recommending a `/usr/bin/exampleos-installer` wrapper. Read issue #437 for related configurability requirements. Done should include an agreed design and implementation path for image-provided installation behavior.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- rust
- Ambito
- cli
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100