fix(nix): Make sure bssl is in the PATH; workaround nix build failure… #2431
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.
Issues:
none
Description of changes:
In some CI environments (in docker containers), the build is trying to write to $HOME, which nix intentionally unsets. This causes build failures with this error:
By setting
$HOME
in preBuild, we can eliminate this failure.Also, the
bssl
utility is not available in a devShell, because we're not properly importingaws-lc
.Call-outs:
The build failure is blocking s2n-tls from using the upstream flake.
Reformatting both nix files with
nix fmt
.Testing:
How is this change tested (unit tests, fuzz tests, etc.)? locally.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.