Running /sbin/entrypoint.sh start-and-exit causes the healthcheck to fail

$ docker compose exec splunk-so cat ../container_artifact/splunk-container.state
started
$ docker compose exec splunk-so /sbin/entrypoint.sh start-and-exit
...
$ docker compose exec splunk-so cat ../container_artifact/splunk-container.state
starting

I prefer to use exec splunk-so /sbin/entrypoint.sh start-and-exit rather than restart splunk-so when I make changes to /tmp/defaults/ because there is less downtime from a splunkd restart than from restarting the whole container.

This issue is a problem because /sbin/checkstate.sh reports that the container is unhealthy unless the state is "running" or "started".

Start by reading /sbin/entrypoint.sh, focusing on the start-and-exit path, then inspect /sbin/checkstate.sh to understand which state values pass the healthcheck. Reproduce the commands from the issue and verify that start-and-exit leaves the container in a state accepted as healthy.