Feature Request

while packaging the software, we noticed that two subsequent builds sometimes produce a slightly different binary. This is probably related to the seccompiler that reads BPF filters definition from resources/seccomp/*.json file and uses an HashMap to store BPF data into a seccomp_filter.bpf blob that gets included in the target.

Describe the desired solution

We suggest using a data structure that preserves the order of insertion, so in the final binary we always get map keys in the same order, enabling to get identical binaries in the build.