Thumbnail .env not respected

[Gemmers0n]

I did a fresh install with the default stack + collabora + traefik.
Some of my newer photos ended up being not displayable, after some digging i found in the container logs "thumbnails: image is too large" logged by the thumbnailer service. So far so good, problem found, indeed my photo dimensions were above the permitted range according to defaults https://docs.opencloud.eu/docs/dev/server/services/thumbnails/environment-variables.

1. I tried to set the ENV with the .env file
   THUMBNAILS_MAX_INPUT_IMAGE_FILE_SIZE=50MB
   THUMBNAILS_MAX_INPUT_WIDTH=12000
   THUMBNAILS_MAX_INPUT_HEIGHT=6000

restarted the container (docker compose down; docker compose up [-d])nothing happening, seems like they needed to get added in the docker-compose as well as they hadn't been in there prior, same error in the logs as since the start.

2. Added to the docker compose:
   THUMBNAILS_MAX_INPUT_IMAGE_FILE_SIZE: "${THUMBNAILS_MAX_INPUT_IMAGE_FILE_SIZE}"
   THUMBNAILS_MAX_INPUT_WIDTH: "${THUMBNAILS_MAX_INPUT_WIDTH}"
   THUMBNAILS_MAX_INPUT_HEIGHT: "${THUMBNAILS_MAX_INPUT_HEIGHT}"

still no success, same error in the logs as since the start.
opened a bash in the container and indeed the ENV VARS were set

3. Tried to go with the default config file dumped into the default config dir (same as the opencloud.yaml) https://docs.opencloud.eu/docs/dev/server/services/thumbnails/yaml-config

webinterface was trying to generate the thumbnails but failed ultimately
Container logs were complainig about inaccessible root_directory: /root/.opencloud/thumbnails (thats the deafult from the config)
For reference my storage config in the .env OC_CONFIG_DIR=/data/config OC_DATA_DIR=/data/files

4. changed root_directory to "/var/lib/opencloud/thumbnails"

Thumbnail generation finally working

Considerations:

• Set the default image resolution to a slightly higher value, i had the problem with a pixel 10 pro 4590x8160 to avoid any tampering with config
• Set a working "root_directory" in the default config file/ ENV VAR
• Even now having it working i'd rather much prefer the .env file approach since it will repeatedly build the same containers even if the config file isn't in place
• Of course root cause analysis why the ENV VARS weren't respected in the first place

All done on OpenCloud 5.1.0 rolling docker image

[micbar]

The .env file is not injected into the container environment. Only the individual config values as used in the env substitution patterns in the compose files. This is by design to prevent arbitrary unsupported settings.

You can put yml file in the custom folder to overload services with your custom config.