Surely this isn't normal?

I’ve always been a Leap user but thought I’d give MicroOS Aeon a try on a Celeron based NUC type device to run nextcloud and an SMB share. I sat down tonight to give GOGS a try too.

Everything was going well before tonight. I had to turn the device off to move it and it seems an auto-update occurred recently… I don’t know when it updated. Maybe 3-4 days ago. I noticed the kernel went from 6.6.7 to 6.6.9.

After the restart the update removed all my auto mount set up (including the LUKS passwords) , deleted all but one group, and it seems to have changed some permissions related to /var/run/docker.sock. Maybe others. Basically, nothing worked after I rebooted.

After an hour of trying I couldn’t get docker to work again.

Snapper rollback fixed everything.

But I’m worried now! I’m not sure what I’ve experienced. A dodgy update?, something I’ve done that will allow this to happen after an update, normal behaviour (!). I’m tempted to go back to the trusty Leap but for such a low powered device that I want to turn on and barely touch MicroOS fits the bill quite nicely.

@OS499846 No, not for Aeon (MicroOS yes) if you did not do anything, it’s a bug… FYI, it’s Aeon, MicroOS is a different openSUSE Product…

Docker isn’t installed on Aeon, do you mean Podman?