docker cannot start containers after reboots
We occasionally see errors like this: https://gitlab.torproject.org/jnewsome/sponsor-61-sims/-/jobs/64984
According to @anarcat, a little while after rebooting these machines, the kernel enters lockdown and will no longer load new modules. If Docker hasn't been used before then, when the runner tries to use it, some kernel modules it needs can't be loaded.
Presumably the right solution here is to add something to the machines' startup scripts such that these modules are loaded eagerly at startup