Incus containers with shifting no longer working after update

Was there a kernel update in the latest Bluefin update? My kernel is currently showing 6.9.4. There is a known issue with Incus where containers no longer work that have the shift="true" idmapping option enabled for the 6.9 kernel version.

Linux 6.9+ idmapping abilities are required but aren’t supported on system

The Incus team has fixed the issue in the Incus 6.2 release but Bluefin is still shipping with 6.1. Due to this my shifted containers will no longer start:

Error: Failed to setup device mount "config": idmapping abilities are required but aren't supported on system

Any plans on updating Incus to 6.2 in an upcoming Bluefin update?

For now I’ll look into rolling back to a previous update. I haven’t tried a rollback yet but wanted to confirm if there was a kernel update in the latest before rolling back. It was working fine prior to the latest update.

EDIT: Yep the kernel was updated. I checked the ujust changelogs and saw this:

kernel 6.8.11-200.fc39.x86_64 -> 6.9.4-100.fc39.x86_64

Can you update and try with the latest image?

Sure thing. Couple questions (edited after some forum searching):

  • What’s the easiest way to update to the latest image? Quick search shows a post by you which says to do rpm-ostree update to get the latest image. Is this still the way to do that?

EDIT: After some searching it looks like the command to switch to the latest image is:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest

I gave this a shot and I rebased to latest rather than the gts image. This is what the rpm-ostree status shows that I’m now running:

ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest
Version: 40.20240618.0 (2024-06-18T23:01:15Z)

Incus is still at 6.1 and didn’t work so I rolled back to the gts image.

- Will updating to the latest image break anything significantly? I suppose if it does I can roll back. I can roll back with no issues.

  • Speaking of rollbacks: is there a way I can “pin” my current image so I can make sure I’m rolling back to the latest with the 6.8 kernel if things go sideways?

EDIT: Looking at the docs helps! sudo ostree admin pin 1

Thanks for all your great work on Bluefin!

ujust update is enough to get you the latest fixes.

You just did a dist-upgrade and back again, that always scares me lol.

Yep I pulled the latest. The 20240619 update is what broke it (bringing in the 6.9 kernel). I did pull 20240620 (with ujust update) prior to trying :latest but that still uses Incus 6.1. Idmapping in Incus 6.1 just doesn’t work with the 6.9 kernel.

I was crossing everything I had hoping I wouldn’t break it. Thankfully I was able to switch back to :gts with no issues. As far as I can tell I didn’t break anything!

It looks like there is a viable solution in that github issue that will work for now (running Incus in a distrobox) that uses Incus 6.2.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.