It appears that any VM launched with OrbStack runs with vm.overcommit_memory=1 and there’s no sysctl.d for it. I’m wondering where it is coming from / why is it enabled? I don’t get the same setup when using podman / docker on a Linux box. So a couple questions regarding this behavior; - where is it set? Seems to come from vinit - Why 1 specifically? - Can I opt into a different mode (and persist it) - What else diverges from a stock Linux box? - Could there be a “prod-fidelity” mode? The issue I’m encountering was debugging an allocation bug that I was hitting in production but could not replicate locally. Thanks for your work on this awesome project

you can change it at runtime