Ephemeral VMs use a small var partition size, without the means of increasing this

Ouverte
#200 3 commentaires 2 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
linux, rust
Domaine
infrastructure

Piste de recherche

Start by tracing how ephemeral VM commands create their /var filesystem and how bcvk libvirt run configures disk sizing; the report also points to crates/kit/src/to_disk.rs near line 551 for the failing installation path. Check the relevant command tests and existing size options before deciding where the option belongs. Done means ephemeral commands can request a larger /var and the reported container pull succeeds; the issue does not identify specific tests.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

good first issue

I have a container and contains a Podman quadlet. This quadlet is configured with Pull=newer. The container doesn't embed the quadlet's image so I can keep my bootc/VM image small.

This seems to pose a problem for bcvk's ephemeral VMs however: per df -h the size of /var is only 780 MiB, but the container image I'm trying to pull for my quadlet is 2+ GiB, resulting in the pull failing due to insufficient disk space.

While bcvk libvirt related commands should allow you to work around that, those don't seem to work either. For example:

bcvk libvirt run --filesystem ext4 localhost/web:latest

This produces:

Creating libvirt domain 'web' (install source container image: localhost/web:latest)
 INFO Creating base disk: "/home/yorickpeterse/.local/share/libvirt/images/bootc-base-26e4d8fee5fcae63.qcow2"
Connected (4 seconds elapsed), beginning installation...
Setting up temporary filesystems...
rm: cannot remove '/var/lib/containers/storage/overlay': Device or resource busy
Error: 
   0: Failed to find or create base disk
   1: Failed to install bootc to base disk: "/home/yorickpeterse/.local/share/libvirt/images/bootc-base-26e4d8fee5fcae63.ecovti.tmp.qcow2"
   2: SSH installation command failed with exit code: Some(1)

Location:
   crates/kit/src/to_disk.rs:551

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

For comparison, building an image with bootc-image-builder and running it with qemu-system does work, though that's only because bootc-image-builder always forces a disk image size of 10 GiB, so it too would likely fail at some point given a sufficient amount of containers to pull in.

To resolve this, the default size of /var should probably be increased and an option for this should be exposed to the various ephemeral related commands, such that you could do something along the lines of bcvk ephemeral run-ssh web:latest --var-size=10G.

Langage dominant
Rust
Étoiles
142
Forks
40
Merge moyen
2 j 22 h
PR mergées (30 j)
10

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

  • Aucun Dockerfile ni fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de bootc-dev/bcvk

Toutes les issues de bootc-dev/bcvk

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.