Containerization is actually a valid strategy to help induce the sleep states necessary for both parent and child process functionality, especially since prolonged operations outside the containerized environment may result in the parent process(es) not passing even the simplest sanity testing.

You really cannot use Containers all the time. When Small Child has been containerized too much you'll run into debugging hell.

Also remote monitoring as available.

BF Skinner's Air Crib might qualify as a containerizing solution. https://www.psychologicalscience.org/observer/skinner-air-cr...