The current template for starting challenges uses a reboot on-failure setting. This can have disastrous effects on stability if multiple challenges that exit immediately on start somehow get started (note: these challenges should be rewritten to not do this, but also not the point) as they start dominating system resources in the container startup process.
Solution
Find and set the knob for "max attempts" so that it gets bounded at a reasonable number of restarts.
Issue
The current template for starting challenges uses a reboot on-failure setting. This can have disastrous effects on stability if multiple challenges that exit immediately on start somehow get started (note: these challenges should be rewritten to not do this, but also not the point) as they start dominating system resources in the container startup process.
Solution
Find and set the knob for "max attempts" so that it gets bounded at a reasonable number of restarts.