Re: Grub2 bootstrap

[Colin Walters <walters verbum org>]

On Tue, Mar 21, 2017, at 08:56 AM, Anton Gerasimov wrote:
  
> OSTree:ERROR:src/libostree/ostree-bootloader-grub2.c:326:_ostree_bootloader_grub2_write_config:
> assertion failed (deployments->len > 0): (0 > 0)

For Fedora (Atomic) we use Anaconda, which is its own world of complexity
and we have some hacks, e.g.:
https://github.com/rhinstaller/anaconda/blob/4670805f77f3dfa391158af1535769b284e7f16e/pyanaconda/payload/rpmostreepayload.py#L318

You're presumably using `ostree admin --sysroot=/path/to/mounted/device deploy` right?
Or are you doing an install inside an existing VM and then saving that?

Is the `/boot/loader` directory in the target directory set up for
ostree correctly as a symlink to a loader.0 directory?

> What is recommended bootstrap procedure for Grub2?

This is a messy topic because how bootloaders are set up vary a lot
across distributions; I'd like the current -grub2.c code to work as
widely as possible of course.

This PR is also likely interesting for you:
https://github.com/ostreedev/ostree/pull/228

One of the major benefits is: "No need to install grub2 package on a target device."

Also on this topic, for Fedora at least we're likely to rework how grub2
works again; there's some terse info in https://github.com/ostreedev/ostree/issues/717
which I hope to fill in more soon.