Skip to content

initrd-setup-root-after-ignition: Ensure /etc/flatcar/sysext exists#89

Merged
jepio merged 3 commits intoflatcar-masterfrom
fix-sysext-mkdir
Mar 13, 2024
Merged

initrd-setup-root-after-ignition: Ensure /etc/flatcar/sysext exists#89
jepio merged 3 commits intoflatcar-masterfrom
fix-sysext-mkdir

Conversation

@jepio
Copy link
Copy Markdown
Member

@jepio jepio commented Mar 12, 2024

Nothing guarantees that this folder is created, so we need to mkdir it before moving the sysext into it. Otherwise the user is forced to create it with ignition when specifying sysexts to install in
/etc/flatcar/enabled-sysext.conf.

@jepio jepio requested a review from pothos March 12, 2024 09:50
jepio added 2 commits March 12, 2024 13:42
Nothing guarantees that this folder is created, so we need to mkdir it before
moving the sysext into it. Otherwise the user is forced to create it with
ignition when specifying sysexts to install in
/etc/flatcar/enabled-sysext.conf.

Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
ZFS provides dracut scripts that get automatically picked up by
dracut/update-bootengine. Explicitly omit the zfs module when calling dracut.

Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
@jepio jepio force-pushed the fix-sysext-mkdir branch from 97b16b7 to 03ab877 Compare March 12, 2024 13:33
The value of ROOT may be interpreted by some scripts in the chroot but is not
correct after chrooting. Unset it before executing chroot.

Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
@jepio jepio requested a review from pothos March 12, 2024 13:55
@jepio
Copy link
Copy Markdown
Member Author

jepio commented Mar 12, 2024

I've pushed two more changes, can you take another look @pothos ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants