Build images with AVIF support

[aentwist]

Related to juliusknorr/nextcloud-docker-dev#177

User Story

I am considering working on adding AVIF preview support to Nextcloud nextcloud/server#13552. I'd like to start the discussion with getting AVIF into the images.

Proposed Solution

Install AVIF in the images that have a PHP GD version that supports it.

Requirements should just be:

• install libavif-dev libaom-dev libdav1d-dev
• configure GD --with-avif

Alternative Considerations

• Have users build it in themselves by using their own images built on top of official images
• docker-php-extension-installer

[aentwist]

The GD extension in PHP 8.1 and later supports AVIF image format

GD extension requires libavif version 0.8.2 or higher.

https://php.watch/versions/8.1/gd-avif

I see that we are currently building images as follows

• NC 24 - PHP 8.0
• 25, 26 - 8.1

However,

Nextcloud 24 is the first major Nextcloud release to work with PHP8.1.

https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_24.html#php8-1

Similarly why is 26 not on 8.2. This situation is going to repeat itself.

In this release support for PHP8.2 was added.

https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_26.html#php8-2

Mentioned in #1950. Is there some reason we are not bumping the versions?

What implications does this have? (Pretty sure the Dockerfile templates are common for 24, 25, 26 right?)

[aentwist]

libaom-dev libdav1d-dev appear to both be for AV1 video. Don't think we need these, although they might be required as peer deps for specific functionality?

[J0WI]

https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html is the source of truth for the recommend PHP versions.

[aentwist]

libaom-dev libdav1d-dev appear to both be for AV1 video. Don't think we need these

We need these.

See juliusknorr/nextcloud-docker-dev#182

[joshtrichards]

When/if upstream (server) suggests this officially in their documentation/requirements we can do so. Since that's not the case today, I'll close this out.