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?

Beginne mit dem stable31-Dienst, der durch docker compose up stable31 gestartet wird, und dem vorhandenen Einstiegspunkt scripts/php-mod-config. Stelle den Modulstatus mit docker compose exec stable31 php -m | grep -i blackfire fest und verfolge anschließend, wie die Neuerstellung des Containers Blackfire konfiguriert. Als erledigt gilt die Aufgabe, wenn ein frischer Container dem dokumentierten Standard folgt und die Einstellung eine Neuerstellung übersteht.