-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fails to start after update #81
Comments
The private key is now owned by a user and group that does not exist:
|
I think this problem was introduced with dc9a4ec. Changing ownership to root does not help. The service might also not have access to Changing the location of the files fixes it!
And updating config.
|
Now
But we know how to fix it! Add
It does not work! Even at Also |
The state is now: trustix.service runs, but the hook crash:
So i think it's just broken at the latest commit. |
Let's see where this issue was introduced. Commit's and errors: 28e221f works (i fixed it)
5577950 same error So this project is broken since august 2022. |
To fix this issue, it needs to be clarified where the keys need to be stored and which permissions they need. For trustix, it works for me to have them in
I haven't figured it out for The solution needs to be added to the documentation. |
I updated my system to NixOS 22.05.4270.b68a6a27adb and trustix from 32ee78a to c852d3c.
After the
nixos-rebuild switch
,trustix-nix-cache.service
andtrustix.service
do not start.Here, for some reason, it can't read the private key anymore.
Maybe this crashes, because the socket does not exist:
I debug it further...
The text was updated successfully, but these errors were encountered: