-
|
Hi, New to zfs and zfsbootmanager but I was able to get a Debian Bookworm install up and running with the official zbm binary on a flash drive. All is well. Now I'm trying to compile my own version with dropbear support. I used the docker build container to generate all the config files, compiled with Specifically, I followed the instructions on https://docs.zfsbootmenu.org/en/latest/general/container-building/example.html#a-simple-host-specific-container-build The only things I customized are as follows:
Everything else is followed exactly. The build logs show that dropbear package is being installed, so I know that part of the config was correct. But not sure if it's actually initialized runtime. After zbm loads and asks for the passphrase, I try to do After the OS loads, I can ssh into the OS at the same IP so it's not a networking issue on the client end. How can I troubleshoot whether dropbear is running or perhaps erroring out? Thanks PS. These are all the files I have in my EDIT: |
Beta Was this translation helpful? Give feedback.
Answered by
ahesford
Feb 16, 2025
Replies: 4 comments
-
|
I partially figured it out. With the provided instructions, somehow the symlink from Here's the output of lsinitrd:You can see in the contents that However, if I change the rc.d script for dropbear from the provided one to a simple one like below, everything works, dropbear starts and listens (lsinitrd shows the files under To further troubleshoot, I added a simple |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I now have a better understanding of the workflow during build. It seems the mkinitcpio function I tested that by modifying the dropbear install hook and adding the following right after Through some errors, I realized that a non-zero exit made the build container output the That code results in: As we can see, If I use my custom rc.d script to copy the keys over to |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I just went back and looked at my initial lsinitrd output and it shows the following: That suggests that the mkinitcpio function When I use copy instead of a symlink, the final EFI image contains an empty Not sure if this is a feature or a bug. If feature, we should perhaps update the zbm docs to copy instead of symlink. If bug, we can report upstream. Please advise. Thanks. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I've also been bitten by this, and just changed my |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
aptalca
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've also been bitten by this, and just changed my
rc.d/dropbearscript to copy the contents of/build/dropbearto/etc/dropbear. Updating the documentation to reflect this seems appropriate.