I rebuilt my Fedora bootc Containerfile, rebuilt and did a bootc switch, kernel panic on reboot
              
              #1411
            
            Replies: 3 comments 4 replies
-
| FWIW the docs on initramfs for Fedora https://docs.fedoraproject.org/en-US/bootc/initramfs/ 
 Impressive, needs debugging. If it is regenerating the initramfs it's probably just running  I bet if you add  BTW, I strongly recommend heredocs. 
 Ah glancing at the code this will happen if you don't have an initramfs at all currently. That's really a bug, we shouldn't conflate a static prepareroot with no initramfs. However ultimately we'll hopefully move to UKIs by default which obviate this. | 
Beta Was this translation helpful? Give feedback.
-
| Some warnings: It's not clear if any of these are causing the issue though... | 
Beta Was this translation helpful? Give feedback.
-
| I think I see what is happening, there's a "dnf update" at some point, leaving us with two kernel versions because there's a new kernel version available. I run 3 random installation scripts here, any of them could be performing a "dnf update". 
 This failed badly for me: https://docs.fedoraproject.org/en-US/bootc/initramfs/ I tried to change the kver line to this: kver=$(ls -1 /usr/lib/modules | sort -V | tail -n1) and dracut was erroring all over the place, so not sure I want to go down that path... The simple fix might be to just add: 
 early in the Containerfile. | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
initrd is missing which made ostree go down this no initrd code path and attempt to boot with initrd=ostree-prepare-root on the cmdline
seems like the addition of
RUN curl -fsSL https://get.docker.com | bashbroke it.Beta Was this translation helpful? Give feedback.
All reactions