do you happen to know why the azure ci runs the container w/ --privileged? i'm checking right now if that solves my issue, but it'll be a harder solve non-locally