Christina W 71d24d6e33 Parse container exit error message instead of status ... The previous implementation in #2170 of parsing the container status was too general, because it relied on the mistaken assumption that a container would have a status of `Stopped` if it was manually stopped. This turned out to be untrue, as manually stopped containers were also getting restarted by the Supervisor due to their inspect status of `exited`. With this, parsing the exit message became unavoidable as there are no other clear ways to discern a container that has been manually stopped and shouldn't be started from a container experiencing the Engine-host race condition issue (again, see #2170). Since we're just parsing the exit error message, we don't need to worry about different behaviors amongst restart policies, as any container with the error message on exit should be started. Change-type: patch Closes: #2178 Signed-off-by: Christina Ying Wang <christina@balena.io>		2023-06-22 14:43:17 -07:00
..
app.spec.ts	Improve tests surrounding Engine-host race patch	2023-06-19 11:11:26 -07:00
network.spec.ts	Create default network as config-only when services have host networking	2022-11-16 10:19:36 -08:00
ports.spec.ts	Migrate simple legacy tests to test/unit and test/integration	2022-10-18 20:36:53 -03:00
service.spec.ts	Improve net alias comparison to prevent unwanted restarts	2023-04-20 14:58:58 -04:00
utils.spec.ts	Parse container exit error message instead of status	2023-06-22 14:43:17 -07:00
volume.spec.ts	Split compose/volume tests into unit/integration	2022-09-28 10:37:40 -03:00