fix(nix): overhaul environment setup for robust devcontainer #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
The Nix environment within the devcontainer sometimes fails to initialize correctly, particularly regarding script paths, user profiles (especially for root), and permissions (e.g., tmp ACLs affecting builds). This can lead to a non-functional Nix shell or errors during container startup or build processes.
Solution:
This PR overhauls the Nix environment setup for increased robustness:
nix-daemonstartup for multi-user mode.direnvactivation directly into the container startup flow./library-scripts) to ensurelibrary-scriptsare consistently found.sudoersconfiguration..nixfiles usingalejandra.Testing:
direnvactivates correctly when an .envrc is present.Note:
These changes primarily address issues encountered for my specific use case but should provide a more reliable base Nix environment for all users of this devcontainer. The commit history has been cleaned and follows Conventional Commits.
Fixes GH Issue #56