9:06 a.m.
On Thu, Mar 3, 2022, at 1:06 AM, Yun Levi wrote:
Hello, all.
I'm trying to install my custom package and mange via ostree.
For this, I try to create some kernel modules and make a branch like below
mkdir -p /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
cp mymod.ko /usr/lib/modules/5.15.18-200.fc35.x86_64/kernel/fs/
ostree commit --base={comomit hash via rpm-ostree status -v}
--branch=test/pkg/mymod .
Hi, what you're trying to do basically is something we're trying to address with
https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md
The reason for the failure is you're committing a whole lot of data that shouldn't
be there, potentially even traversing into `/var`.
People have asked a lot for us to make it easier on the ostree side to do exactly what
you're trying here, but there's a lot of subtleties. The core problem is this
"commit from current commit" will end up creating hysteresis (
https://blog.verbum.org/2020/08/22/immutable-%E2%86%92-reprovisionable-an... )
- the state of the new system depends on the current one.
But what you really want is to be able to re-apply your changes on top of a new base, and
that's where we're going with the ostree native container flow - as a bonus the
result will be a standard container image one can push around, verify in CI etc.