I followed the instructions here (
https://salsa.debian.org/debian/ostree/-/blob/debian/latest/debian/ostree-boot-examples/README.md)
to test ostree on a minimal sid VM with a separate boot partition. When I
tried rebooting into the new ostree image, the boot failed, and grub
reported an error about not being able to find vmlinuz-*.

I believe the underlying issue is that the grub cfg generated when I
deployed the ostree image was incorrectly trying to find the kernel under
/ostree/* instead of /boot/ostree/*. Applying the attached patch fixed the
problem, though I am unfamiliar with this code, so there may be a better
solution.

I'm surprised that this worked, because grub configuration normally needs
to list paths relative to the root of the /boot partition, not paths
relative to the root of the overall system (which makes sense, because
grub runs before any partitions have been mounted, and is acting on an
individual partition's filesystem).

Please could you talk to upstream about this, on their bug tracker at
<https://github.com/ostreedev/ostree/issues>?

I don't use ostree system-wide myself (my use-case for it is as a backend
for Flatpak) so I am not really able to provide support for that use-case,
and I suspect that the ostree-boot README is outdated.

    smcv