You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #673 the topic of producing a bootc image from the same build system that produces ostree commits was discussed, where it was noted that rpm-ostree compose container-encapsulate could be used to generate an OCI image from an ostree commit.
This got me thinking on a tangent about the feasibility of producing an OCI image via rpm-ostree compose container-encapsulate which is identical to an OCI image produced by podman build and a Containerfile with FROM quay.io/fedora/fedora-bootc:40 etc
Is this kind of reproducibility a goal or would it just be a neat party trick? I wonder if it would be useful to ease the migration from a "pure" ostree solution (i.e. RHEL for Edge) to a bootc solution.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In #673 the topic of producing a
bootc
image from the same build system that producesostree
commits was discussed, where it was noted thatrpm-ostree compose container-encapsulate
could be used to generate an OCI image from an ostree commit.This got me thinking on a tangent about the feasibility of producing an OCI image via
rpm-ostree compose container-encapsulate
which is identical to an OCI image produced bypodman build
and a Containerfile withFROM quay.io/fedora/fedora-bootc:40
etcIs this kind of reproducibility a goal or would it just be a neat party trick? I wonder if it would be useful to ease the migration from a "pure" ostree solution (i.e. RHEL for Edge) to a
bootc
solution.Beta Was this translation helpful? Give feedback.
All reactions