initramfs fails to build image with lvm in $PATH
#213
Comments
|
Unrelated, but my disk is bound to |
|
Note: I am using booster 0.10 |
|
Booster does add It adds the |
|
Note that you can use |
|
@StratusFearMe21 what Linux distro do you use? |
|
I use Artix Linux with the s6 init system |
|
|
It is really weird then. Booster uses Let's start debugging this problem. Could you please provide output of Then I will add extra debug statements to booster source code so you can compile it, then run and get more information about files booster finds. |
|
Sure, I've optimized my config a little since I opened this, but the problem still stands modules_force_load: padlock_aes,aesni_intel,xts,amdgpu
universal: false
compression: lz4
strip: true
extra_files: /usr/bin/lvm
enable_lvm: trueThis is what I get with this config And this is without I notice that in the second list, |
|
Interesting development. It appears that my |
|
Looking at my |
anatol
added a commit
that referenced
this issue
Mar 24, 2023
Until now we used `exec.LookPath` golang function to lookup binaries. This function depends on user's $PATH envvar and the order directories specified there. This could mess with our image symlink tree. What we want is to make sure that we lookup/add files at non-symlinked directories first (i.e. /usr/bin). Closes #213
|
I propose a different solution. Do not rely on user's $PATH at all, and always lookup in I pushed a potential fix to |
Yep, it explains the issue. |
anatol
added a commit
that referenced
this issue
Mar 24, 2023
Until now we used `exec.LookPath` golang function to lookup binaries. This function depends on user's $PATH envvar and the order directories specified there. This could mess with our image symlink tree. What we want is to make sure that we lookup/add files at non-symlinked directories first (i.e. /usr/bin). Closes #213
|
Yep, the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When booting with this initramfs, it fails because it can't find the
lvmexecutable in it's$PATH. Extracting the generated initramfs usingunzstd, followed bycpio -i, shows that booster did not include thelvmbinary in the initramfs, despite there being an entry for it in the cpio archiveThis is my config
Adding the config value
Seems to fix the issue.
This config value
Does not fix the issue
Also worth noting is that booster fails to create a /usr/bin directory as well, which results in a broken
/binsymlink. This problem may be the result of booster's generator trying to to put thelvmbinary atbin, which is a broken symlinkThe text was updated successfully, but these errors were encountered: