Testing built sysexts

[jo5huajohn]

Hello,

I've been learning about sysexts and created one for vagrant - a tool I use frequently. I was able to write a Containerfile and justfile and build it successfully. However, I can't seem to install it and can't find any documentation on doing so.

So far, I've been copying the generated raw file to /var/lib/extensions.d and then symlinking it to /var/lib/extensions. In my case:

/var/lib/extensions.d    vagrant-2.4.7-0-2.4.7-1-42-x86-64.raw
/var/lib/extensions       vagrant.raw

systemd-sysext-list returns the following output:

NAME        TYPE PATH                                TIME                       
erofs-utils raw  /var/lib/extensions/erofs-utils.raw Mon 2025-05-26 17:58:04 +04
vagrant     raw  /var/lib/extensions/vagrant.raw     Thu 2025-07-03 18:56:11 +04

When I restart systemd-systemext.service, it fails with the following errors:

Jul 03 19:25:51 fedora systemd[1]: Starting systemd-sysext.service - Merge System Extension Images into /usr/ and /opt/...
Jul 03 19:25:51 fedora systemd-sysext[59851]: Failed to read metadata for image vagrant: No medium found
Jul 03 19:25:51 fedora systemd[1]: systemd-sysext.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 19:25:51 fedora systemd[1]: systemd-sysext.service: Failed with result 'exit-code'.
Jul 03 19:25:51 fedora systemd[1]: Failed to start systemd-sysext.service - Merge System Extension Images into /usr/ and /opt/.

I found this link that stated a reason for this issue, but I don't think I'm facing the same one.

Where am I going wrong and is there anything I'm missing?

[travier]

Can you make a PR / link to your justfile? The extension name must match the file name.

[jo5huajohn]

Please refer to: #142