RFE: Provide mount API to copy content from the container. Specifically /opt content.

Ouverte
#2,433 1 commentaire 0 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é
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
30/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
rust

Piste de recherche

Commencez par Discussion #1038 et le comportement existant de bootc image et du deployment décrit dans cette issue. Définissez l’interface de mount et d’unmount, le cycle de vie, les garanties de lecture seule, l’accès aux versions staged par rapport aux versions booted, l’intégration avec systemd et le comportement en cas d’image manquante ; le travail est terminé lorsque cette sémantique est spécifiée et implémentée avec une couverture appropriée.

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

Description

Some users have applications that install under /opt. Existing approaches and their trade-offs are discussed in Discussion #1038.

When /opt resolves to persistent /var/opt, whether through a symbolic link or a bind mount, its contents become persistent, user-managed state. Application content initialized there during installation is therefore not replaced during subsequent bootc switches or upgrades.

We do not want to change bootc’s contract: bootc should not modify or merge /var after installation. Doing so could overwrite user data and create ambiguous rollback behavior.

However, bootc could provide a supported mechanism for accessing selected content from the booted or staged container image. An application or administrator could then either copy that content into /var or
mount and consume it directly.

A conceptual interface might be:

bootc image mount
--deployment booted
--source /opt/example-agent
--target /run/example-agent-image
--read-only

An application-specific migration service could then copy it:

rsync -a
/run/example-agent-image/
/var/opt/example-agent/

Alternatively, the image content could be mounted directly at an explicitly selected location under /var:

bootc image mount
--deployment booted
--source /opt/example-agent
--target /var/subdir/example-agent-image
--read-only

The application could use this location for its immutable binaries while keeping configuration, logs and other writable state elsewhere under /var.

This preserves the existing ownership contract:

  • bootc does not merge, delete or overwrite persistent /var content.
  • Image content is exposed read-only.
  • The administrator explicitly selects both the source and target.
  • Applications own any synchronization or migration policy.
  • Rollback and persistent-state compatibility remain application decisions.

The API should define:

  • Access to both booted and staged deployment content.
  • Read-only enforcement.
  • Whether the target must be an empty mount point.
  • Mount lifetime and explicit unmount behavior.
  • How the mount is recreated during boot.
  • Integration with systemd service ordering.
  • Behavior when the source path does not exist.
  • Behavior when the original container image is no longer locally available.
  • Upgrade and rollback semantics.

A possible systemd integration could look like:

[Unit]
Description=Expose image-owned agent content
Before=example-agent.service
RequiresMountsFor=/var/subdir

[Service]
Type=oneshot
ExecStart=/usr/bin/bootc image mount --deployment booted --source /opt/example-agent --target /var/subdir/example-agent-image --read-only
RemainAfterExit=yes
ExecStop=/usr/bin/bootc image unmount /var/subdir/example-agent-image

[Install]
WantedBy=multi-user.target

The goal is to make content already delivered through the bootc image accessible without:

  • Automatically modifying /var.
  • Pulling the same image again with Podman.
  • Requiring applications to duplicate their complete payload elsewhere in the image.
Langage dominant
Rust
Étoiles
2.3k
Forks
230
Merge moyen
2 j 11 h
PR mergées (30 j)
42

Préparer son environnement

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/bootc

Toutes les issues de bootc-dev/bootc

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.