Blackfire enabled by default?

Hi, I've noticed a lot of php_network_getaddresses: getaddrinfo for blackfire failed: Name or service not known errors in the nextcloud logs. A quick search surfaced this older issue, which discusses the same: https://github.com/juliusknorr/nextcloud-docker-dev/issues/57

In the end, a changelog entry was referenced, stating that blackfire (and xdebug) should be disabled by default, with scripts to enable / disable them. However, it seems that this is not the case (any more?).

When I start a fresh set of containers (e.g. docker compose up stable31), I see blackfire enabled (docker compose exec stable31 php -m | grep -i blackfire). I can use ./scripts/php-mod-config stable31 blackfire off to disable it, that seems to work. But whenever I recreate the container, it comes back and I have to manually disable again.

• Shouldn't blackfire be disabled by default?
• Is there a simple way to permanently disable blackfire that persists container re-creation?

Start with the stable31 service invoked by docker compose up stable31 and the existing scripts/php-mod-config entry point. Reproduce the module state with docker compose exec stable31 php -m | grep -i blackfire, then trace how container recreation configures Blackfire. Done means a fresh container follows the documented default and the setting persists across recreation.