Micah Abbott

I think this is generally broken for the Atomic Desktops. I tried following (most of) the root password recovery steps from the generic Fedora docs and they were not successful....

I found that changing my user password via `passwd` in a normally booted system worked for me without any additional steps. :shrug:

> 3. `chroot /sysroot` On a freshly installed Silverblue 39 VM, I'm getting `chroot: command not found` Might be a different experience on ublue-os derived hosts?

> > ``` > > 3. `chroot /sysroot` > > ``` > > On a freshly installed Silverblue 39 VM, I'm getting `chroot: command not found` > > Might be...

> Ah...I found it at `/sysroot/usr/sbin/chroot` When using the instructions above and replacing the `chroot` with the full path I found, these instructions appear to work successfully on a Silverblue...

IMO, I would start with a similar output to what we have in `rpm-ostree status` ``` $ rpm-ostree status State: idle AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 6h ago Deployments: ostree-image-signed:docker://ghcr.io/miabbott/rh-meatwad:latest...

> Also need to investigate whether rpm-ostree supports these new compression types yet. I'm fairly certain the container handling code in `rpm-osteee` is using `skopeo` or the `containers/image` library, so...

Comment from @jlebon that was made on original issue (https://github.com/dracutdevs/dracut/issues/2656) : > OK yeah, I thought FCOS/RHCOS didn't actually use the initramfs on shutdown. And it doesn't by default, but...

This looks like a temporary mirror issue...I was able to successfully retrieve some of the RPMs that were returned HTTP 503. I would be curious if we re-ran the CI...

As part of whatever kargs support is implemented, we should consider how to support per-architecture kargs. For example, console settings; see the discussion on the MR from @trgeiger - https://gitlab.com/bootc-org/examples/-/merge_requests/11#note_1783996244