rpm-ostree update Pulling manifest: ostree-unverified-registry:quay.io/fedora-ostree-desktops/kinoite:rawhide error: Creating importer: skopeo proxy unexpectedly exited during request method Initialize: exit status: 127 setpriv: landlock_create_ruleset failed: Keine Nachricht des gewünschten Typs ("no message of requested type")
OS: Fedora Linux 40.20240212.0 (Kinoite Prerelease)
as a workaround sudo rpm-ostree rebase --reboot fedora:fedora/rawhide/x86_64/kinoite works. I love how easy Kinoite is. :D
sudo rpm-ostree rebase --reboot fedora:fedora/rawhide/x86_64/kinoite
IIUC this is an issue with the new util linux in rawhide. See https://github.com/coreos/fedora-coreos-tracker/issues/1666
Metadata Update from @siosm: - Issue assigned to siosm - Issue set to the milestone: Fedora Linux 40 - Issue tagged with: kinoite
I started running into this issue a few days ago as well. When trying to upgrade Fedora Kinoite nightly via Discover, the update is almost immediately aborted and the following error message is displayed:
rpm-ostree transaction failed with: error: Creating importer: skopeo proxy unexpectedly exited during request method Initialize: exit status: 127 setpriv: landlock_create_ruleset failed: No message of desired type
Output of rpm-ostree status:
rpm-ostree status
schuyler@Schuyler-LT:/var/home/schuyler$ rpm-ostree status State: idle Deployments: ● ostree-unverified-registry:quay.io/fedora-ostree-desktops/kinoite:rawhide Digest: sha256:4f9976fde2f6de7f709424f10938124eb22b4fd09dbaf155bd169c573335f1a4 Version: 40.20240211.0 (2024-02-11T01:18:19Z) LayeredPackages: rpmfusion-free-release rpmfusion-nonfree-release steam-devices ostree-unverified-registry:quay.io/fedora-ostree-desktops/kinoite:rawhide Digest: sha256:6a449fdd5e9c3e1ff9a98c67dc361ab0df1d5d98b9bb27e6f253e61cbdebdc1a Version: 40.20240130.0 (2024-01-30T01:21:52Z) LayeredPackages: rpmfusion-free-release rpmfusion-nonfree-release steam-devices fedora:fedora/39/x86_64/kinoite Version: 39.20231221.0 (2023-12-21T02:20:24Z) Commit: 14048bb3d32145a48f91d5c098801f5b0da8c12469bf86f4f6fd3de6b29a4fc0 GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C Pinned: yes
This should be fixed now according to https://github.com/coreos/fedora-coreos-tracker/issues/1666#issuecomment-1960697746
Metadata Update from @siosm: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)