Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
deployment.autoLuks deprecation #62211
This issue is a placeholder for all those users raising their voices in response to the deprecation of NixOps
Please let us know if you are using the feature!
Even in its current state it seems to be halfway broken (e.g. removing a LUKS device panics systemd), and people expressed doubts on whether it's being used at all.
Looking at the NixOps repository and searching for public infrastructure repositories didn't yield a large (or any) userbase of the feature. Thus we are asking for feedback if you are using it.
The changes previously done to our systemd fork included changes to the startup unit ordering. The local filesystems were no longer part of the very basic system init, allowing sshd and similar processes to start without finishing all mount units.
Due to those relaxed boot requirements a bunch of errors with state and runtime directories appeared. There were some fixes but they are still incomplete (e.g.
Why did this become necessary?
In the past our systemd fork carried a patch (NixOS/systemd@ce79214) that removed the
Systemd didn't support
Since systemd supports managing
While probably not noticeable for most people there is a race condition between the folders in
Besides those, we are trying to reduce the amount of custom patches that are being applied to systemd. In the long run it should become easier to maintain our systemd package. Eventually we would like to upstream some of our changes in a portable way. Things that aren't strictly required for systemd to work on NixOS should therefore go away.
What can I do to make it work again?
Make sure you add
Do not forget to read the error message you got and set the option that was mentioned there.
That's what the mount(8) says about it: