hermes-s6-container-supervision

Create a directory under docker/s6-rc.d/<name> with a type file containing longrun and a run script using #!/command/with-contenv sh. Add empty dependencies.d/base and user/contents.d/<name> files so it joins the user bundle, and the Dockerfile COPY picks it up automatically.

Run docker exec with the absolute path /command/s6-svstat /run/service/<name> to see its state. A down status with an exitcode and 'want up' means s6 keeps restarting a crashing process; check the service logs and configuration to find the cause.

The /command directory containing s6-overlay binaries is only on PATH for processes spawned by the supervision tree, not for docker exec sessions. Always invoke the absolute path /command/s6-svstat or /command/s6-svc when running commands via docker exec.

Exit code 143 occurs because /run/s6/basedir/bin/halt does not propagate the exit code written to the container results file, so shutdown always reports SIGTERM. To get a real exit code, let the CMD program exit normally instead of calling halt from a finish script.

Service directories under /run/service live on tmpfs and are wiped on container restart. They are recreated by the cont-init.d reconciler at boot; if a slot is missing, check docker logs for the 02-reconcile-profiles script output.