S6_BEHAVIOUR_IF_STAGE2_FAILS=2 ignored

[frenck]

Setting S6_BEHAVIOUR_IF_STAGE2_FAILS=2 is ignored, introduced in v2.2.0.0.

This setting should send a termination signal to the supervision tree. Before v2.2.0.0 it did.

If a script during stage 2 fails (in my case cont-init.d) with a non-zero exit code, it just continues now. See the example output below:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] glances.sh: executing... 
FATAL: PROTECTION MODE IS ENABLED!
FATAL: 
FATAL: To be able to use this add-on, you'll need to disable
FATAL: protection mode on this add-on. Without it, the add-on
FATAL: is unable to access Docker.
FATAL: 
FATAL: Steps:
FATAL:  - Go to the Supervisor Panel.
FATAL:  - Click on this add-on.
FATAL:  - Set the 'Protection mode' switch to off.
FATAL:  - Restart the add-on.
FATAL: 
FATAL: Access to Docker allows you to do really powerful things
FATAL: including complete destruction of your system.
FATAL: Please, be sure you know what you are doing before
FATAL: enabling this feature (and this add-on)!
FATAL: 
[cont-init.d] glances.sh: exited 1.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting Glances...
INFO: Starting NGinx...

in the above cont-init.d/glances.sh exits with 1.