Add support for Windows

Aperta
#162 4 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
Da chiarire
Stato di attività
Ferma
Stack tecnologico
rust

Direzione di ricerca

This is an exploratory epic, not a scoped implementation task; it points to the experimental bcvk_win POC and the separate to_disk on Windows issue #165. Start by reviewing that issue and the POC’s stated constraints: Hyper-V, Podman with a WSL machine, Macadam, and a bootc image with hyperv-daemons. The epic does not define a completion criterion; Windows support scope and project direction remain open questions.

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

Descrizione

Following my chat with Colin, I am opening this issue to track the exploration of enabling Windows for bcvk.
This issue serves as a high-level overview of the initial POC and a discussion point for the direction we want to take.

During DevTools week I have implemented a CLI POC that allows the project to work on Windows using Hyper-V.

  • POC branch (experimental): Link
  • main branch (a bit more polished/rebased on upstream): Link

the POC is very limited and only implements the to_disk and hyperv run commands. They are very far from the upstream implementation. My intent was more to put my hands over rust. It's not ready for testing as it is tightly coupled with my local setup. It requires podman to have a machine on WSL, macadam to be installed and that the bootc image to have the hyperv-daemons package in it.

This issue will be used as an Epic to track sub-issues that provides a minimal support on Windows.

@cgwalters if you prefer to not have any epic you can close it. I opened this as it was the only way i thought to give a quick overview why i was targeting windows.

Were you envisioning to have the windows implementation here or keep a separate project as it could be implemented slower than the linux version?
FYI in the bcvk_win main branch i tried to add my commits over bcvk.

Which is the minimal support bcvk should provide on Windows? Bootc VHD/VHDX image creation + running a permanent Hyper-v VM with that image? I'll open an issue for each command to separate discussions and avoid confusion.

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.