Support executing `install to-filesystem` from host directly
- Vorherrschende Sprache
- Rust
- Sterne
- 2.3k
- Forks
- 230
- Ø Merge
- 3 T. 12 Std.
- Gemergte PRs (30 T.)
- 38
Beschreibung
As someone who used the workflow of "install to-filesystem" to get a system compatible with bootable containers. I used the following command (successfully):
```
$ sudo yum install -y podman
$ sudo podman run --rm --privileged --pid=host --security-opt label=type:unconfined_t -v /:/target
-v /var/lib/containers:/var/lib/containers quay.io/swalter/monday:1.0 bootc
install to-filesystem --karg=console=ttyS0,115200n8 --replace=alongside /target
$ sudo reboot
```
This command is not discoverable. I would have expected the to use the ```bootc``` command directly, or have a much simpler podman command.
Beitragsleitfaden
Rechercherichtung
Start by reviewing the existing `bootc install to-filesystem` entry point and the documented container invocation shown in the issue. Define how the operation should be invoked directly from the host or through a simpler Podman command, then verify that it preserves the requested kernel arguments, replacement mode, and target filesystem behavior.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- cli, operating-systems
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100