google-compute-image: fix Yama LSM option conflict #24267
Merged
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.
Having fixed the Google Compute Engine image build process's copying
of store paths in PR #24264, I ran
nixos-rebuild --upgrade switch
...and the GCE image broke again, because it sets the NixOS configuration
option for the sysctl variable
kernel.yama.ptrace_scope
tomkDefault "1"
, i.e., with override priority 1000, and now thesysctl
module sets the same option tomkDefault "0"
(this waschanged in commit 86721a5).
This patch raises the override priority of the Google Compute Engine
image configuration's definition of the Yama sysctl option to 500
(still lower than the priority of an unmodified option definition).
I have tested that this patch allows the Google Compute Engine image
to again build successfully for me.