Add network isolation support

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

I maintainer di solito rispondono entro 2 giorni

@jeckersb ci sta già lavorando.

Dal 8/8/2026.

  • #311 di @jeckersb — aperta

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
rust

Direzione di ricerca

Start by reading the bcvk VM provisioning and networking code, especially the libvirt integration and the existing bcvk libvirt ssh path; the issue does not name specific files or tests. Determine how to block guest outbound access while preserving host-to-VM connectivity, and account for how staged resources could later be exposed. Done means the VM cannot reach arbitrary internet services while host SSH access still works; linked pull request #311 is already open.

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

Descrizione

(This issue is meant to describe the problem, sketch out requirements, and propose one or more solution(s) in order to be fed into a LLM for initial implementation)

Currently bootc tmt integration tests run inside of a bcvk-provisioned VM. However, this VM has general network access to the outside world. That means the test environment can pull arbitrary data at execution time. We are currently trying to reduce the number of testing flakes in bootc CI. A common source of error is the tests pulling container images from quay.io from inside of the VM. This is problematic because it may be many hours into a CI run before a given test is run and encounters a flake, which invalidates the hours of testing that happened beforehand. It should be noted that although quay.io flakes are the most common, there are other flakes both known and unknown that can also occur from within network-enabled test runners.

The general idea then is to enable support in bcvk to disable as much network as possible. Probably it is sufficient to disable outbound routing from the VM, but other options such as manipulating firewall rules could be considered as well. Care must be taken to ensure connectivity between the host and VM is preserved; for example it should still be possible to bcvk libvirt ssh into the VM from the host, but once inside the VM it should not be possible to connect to arbitrary services on the internet.

A followup to this is to pre-stage any required resources on the test runner host (container images, packages, etc.) and expose those resources into the VM. The network isolation support implementation should take into consideration how those resources are exposed to the VM. I suspect that will likely be handled directly on the filesystem via virtiofs, but it could also be feasible to expose network resources from the host onto the VM. As an example, maybe container images are pulled into the host containers-storage, and then the host re-exports those to the VM via a container registry which is reachable via the local network.

This would make the test execution environment more hermetic and similar to something like mock where the inputs (source, spec, buildroot) are populated at the beginning, and then once the build executes it does not have network access.

This a forcing function to make sure all testing inputs are accounted for beforehand. It should greatly cut down on the number of network failures that happen deep into CI runs. If all needed resources are collected at the beginning of the CI pipeline, this means that any flakes or outages in dependent services will be encountered early and should hopefully cause the pipeline to fail on the order of minutes, instead of hours. It also gives us a common place to implement retry logic in order to tolerate transient network errors.

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.