I added steps to move container image updates around with skopeo and apply them with bootc. Please double check that this is correc! It works really well on my side, but I'm unsure if bootc edit is a better option for changing where the update is pulled from.
I was a bit confused into thinking our `-dev` images had
`root.transient` on, but they don't quite right now because
we don't regenerate the initramfs after installing the updated
ostree in that image.
However, because bootc-image-builder today is throwing away
the immutable bit on `/` (a different bug, see
https://github.com/ostreedev/ostree/pull/3094 ) we actually...
amazingly get a very similar effect in practice!
Anyways, let's go ahead and describe filesystem state here.
There is some overlap with `install.md`, but that doc is all about
how to just get started.
This doc aims to cover things that are somewhat different about
the base image we ship here versus just what one might get
from installing the same RPM packages.
The automatic updates being on by default is a big one.
Signed-off-by: Colin Walters <walters@verbum.org>
Colin Walters
Liora Milbaum
Ben Breard