Blackfire enabled by default?

[NikolausDemmel]

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: #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?

[juliusknorr]

Thanks for raising this. I think having it disabled by default makes the most sense.

I guess for some reason the renaming of the config during the container build does not have the expected effect:

nextcloud-docker-dev/docker/Dockerfile.php.template

Line 70 in a7990a9

&& mv /usr/local/etc/php/conf.d/docker-php-ext-blackfire.ini /usr/local/etc/php/conf.d/docker-php-ext-blackfire.ini.disabled \

[NikolausDemmel]

Is there a way to permanently disable blackfire in a way that survives container re-creation, given the current docker images?

[juliusknorr]

I pushed a quick fix to 305e9ab, images may take a bit to build but should be available later today

[juliusknorr]

Ok that did not yet work as expected, /usr/local/etc/php/conf.d/docker-php-ext-blackfire.ini is still active