From reading the logs my initial theory is that the “shim started” / “shim reaped” messages are due to a crashloop of the container engine itself; the shim is just a part of the container runtime which is symptomatic of container starts/stops (so, yes, completely normal for containers that are not restarting, or are restarting but then the container engine exits). As for debugging the root cause, logs show that balenad is exiting with pthread_create failed: Resource temporarily unavailable. Do either of alexgg’s bullet points in this thread comment apply to your case?