On 25 Oct 2018, at 15:40, Peter Robinson <pbrobinson(a)gmail.com>
wrote:
On Thu, Oct 25, 2018 at 12:51 PM Tim Coote <tim+fedoraproject.org(a)coote.org>
wrote:
Hullo
given the challenges of working out how `(rpm-)ostree` works for overlaying packages on
‘real hardware', I thought I’d try to build a vagrant box for x86 version of fedora. I
can see that there are issues with getting VBoxGuestAdditions installed as they don’t use
a package manager, but just try to create symbolic links into `/usr/bin`. I’m assuming
that I’ll be able to work around that with `ostree admin unlock —hotfix`.
However, there seem to be some inconsistencies in the packages in the ostree.
$ rpm -qa |grep kernel kernel-devel-4.18.16-300.fc29.x86_64
kernel-tools-libs-4.18.10-300.fc29.x86_64 kernel-modules-4.18.12-300.fc29.x86_64
kernel-tools-4.18.10-300.fc29.x86_64 kernel-headers-4.18.16-300.fc29.x86_64
kernel-4.18.12-300.fc29.x86_64 kernel-core-4.18.12-300.fc29.x86_64
Note that kernel{,-core,-modules} are at version 4.18.12, whereas kernel-{devel,headers}
are at 4.18.16
Is this expected? Is there a workaround, or am I stumped on getting VBGuestAdditions onto
the vagrantbox?
It's certainly possible and it should make no difference.
Also you don't need to build the VBox third party bits in Fedora any more as all the
kernel modules are in the Fedora kernel, you just need to do "rpm-ostree install
virtualbox-guest-additions" and you'll have everything needed.
Thanks. That will help. I’d been using a standard bento packer builder for fedora, which
had its own view of how to install VBGuestAdditions. That approach may still be required
as vagrant tries to use the version of VBoxGuestAdditions that’s on the host running
virtualbox.
Is there anywhere that I can look to understand the relationship between the different
images?
It would be helpful to put some more automation around the creation of the image that gets
loaded onto SDCards (eg
https://u8538325.ct.sendgrid.net/wf/click?upn=0nhH4OIYFtatOO7tDf-2BEy9hRd...
in much the same way that kickstart/anaconda works with installation .iso’s.
Ideally, I’d combine that with pxe boot to take the SDCards out of the loop, but at least
eliminating connecting a monitor up to the pi is a start. I appreciate that I can
`rpm-ostree upgrade`, but I’d like to get a reproduceable process for user creation,
layered packages, systemd services, etc as they are far from stable for me.
Tim