-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to test luks setup with --vm-test
#575
Comments
There is no trick as of today. Those VMs also run in a nix-build, which would require adding secrets. Maybe there could be a way to allow stub secrets for testing. |
Thanks for the quick answer! Yeah, stub secrets would be great! |
@Lassulus could we recursively override all existing cryptsetup keys with fake keys? Same for zfs. |
Not sure how could provide these keys at boot time... |
maybe https://systemd.io/CREDENTIALS/
|
Is there any trick how I can test a luks setup with
--vm-test
. Doing so always fails to unlock the luks device in thebooted_machine
stage of course, because the key files are missing.The text was updated successfully, but these errors were encountered: