You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 2 calls step 3 with exec. However, step 1 does not use exec when calling step 2. It also doesn't trap SIGTERM. This causes an issue downstream in dockerfile/rabbitmq, which adds a step 0 script at /usr/local/bin/rabbitmq-start:
Is there any reason why exec is missing at step 1(/usr/sbin/rabbitmq-server)? It breaks the chain, causing issues with SIGTERM handling when RabbitMQ is run in a container.
The text was updated successfully, but these errors were encountered:
When starting RabbitMQ, the flow looks like this:
/usr/sbin/rabbitmq-server
(https://github.com/rabbitmq/rabbitmq-server/blob/master/packaging/common/rabbitmq-script-wrapper)/usr/lib/rabbitmq/bin/rabbitmq-server
Step 2 calls step 3 with
exec
. However, step 1 does not useexec
when calling step 2. It also doesn't trap SIGTERM. This causes an issue downstream in dockerfile/rabbitmq, which adds a step 0 script at/usr/local/bin/rabbitmq-start
:Is there any reason why
exec
is missing at step 1(/usr/sbin/rabbitmq-server
)? It breaks the chain, causing issues with SIGTERM handling when RabbitMQ is run in a container.The text was updated successfully, but these errors were encountered: