[Question] Disabling service within service itself about s6 HOT 5 CLOSED

If it's a Docker image then they're likely using s6-overlay, which internally uses s6-rc already. :-)

from s6.

Ah, indeed they're not using s6-overlay. Using pure s6 is entirely fine here - it just doesn't have the same purpose, and in this case there should be a different place in the container's run scripts where you can run your oneshot.

from s6.

Controlling a service from within itself works and is supported, but is bad practice and generally a sign that you are abusing the pattern and need to redesign something.

Here you are using a supervised service to perform work that must only be done once. This is a misuse of s6; oneshot scripts are not meant to be supervised, and s6 is not the right tool to run your script. If you need to run it in an init sequence, for instance, the right tool for you to use would be s6-rc.

GitHub is not the place where we host s6 discussions. For more support, please join the supervision mailing-list. Thanks.

from s6.

In my case the docker image is outside of my control, so the service "terminating itself" is the only simple/reasonable option. I'm glad it's supported.

I will look into s6-rc. Thanks for the advice!

from s6.

I don't think so, but I will tell them to look into it. Thanks for the tip.

from s6.