OPCache not enabled

[Naeaeaeaeae]

php -r "
if (function_exists('opcache_get_status')) {
$s = opcache_get_status(true);
echo 'OPcache: ' . ($s['opcache_enabled'] ? 'ENABLED' : 'DISABLED') . PHP_EOL;
} else {
echo 'OPcache Module NOT LOADED' . PHP_EOL;
}
"

OPcache: DISABLED

After coping the opcache-recommended.ini over to opcache-z-99.ini

php -r "
if (function_exists('opcache_get_status')) {
$s = opcache_get_status(true);
echo 'OPcache: ' . ($s['opcache_enabled'] ? 'ENABLED' : 'DISABLED') . PHP_EOL;
} else {
echo 'OPcache Module NOT LOADED' . PHP_EOL;
}
"

OPcache: ENABLED

And better performance, so something was not right.

https://apps.truenas.com/catalog/nextcloud/

php -v
PHP 8.3.30 (cli) (built: Feb 3 2026 02:35:02) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.30, Copyright (c) Zend Technologies
with Zend OPcache v8.3.30, Copyright (c), by Zend Technologies

Version
Nextcloud Hub 25 Autumn (32.0.5)

[joshtrichards]

The opcache is enabled outside of the CLI-mode.

For the CLI though, opcache.enable_cli hasn't been the default nor recommended upstream for a long time. (I'm guessing maybe you have an old or customized opcache-recommended.ini if that "fixed" this for you).

And better performance, so something was not right.

Can you be more specific?

Since CLI processes are nearly always one-off, there's no benefit (opcache isn't shared) and usually a downside (since compiling takes extra time).

Off the top of my head:

• It may be relevant for long running (i.e. semi-permanent/persistent processes) such as if using the Nextcloud worker -- which is an advanced Nextcloud scenario and outside the scope of the Docker image); and, in any case, easily forced for just the worker by using php -d opcache.enable_cli=1 or similar.
• It might be relevant in terms of impeding JIT for long running CPU bound tasks, but only if those are being ran from the command-line. And, again, those can be selectively enabled since having it on all the time would be a negative.

If a recommended config change should be considered for Nextcloud, it should be explored upstream (by https://github.com/nextcloud/server and https://github.com/nextcloud.documentation) first. We try to stick to what's documented.