bitnami-containers/bitnami/nginx/1.29/debian-12
Andrea Pilo a1b98046f2
[bitnami/nginx] Fix include order for context.d/http ConfigMaps (#90678)
When using the Bitnami nginx Helm chart with existingContextHttpConfigmaps
to define log_format or map directives, nginx fails to start because
server_blocks are included before context.d/http files.

This issue occurs because the current nginx.conf includes server blocks
first, which try to reference directives (like log_format) that haven't
been loaded yet from context.d/http ConfigMaps.

This change swaps the include order so that context.d/http/*.conf
loads first (defines log_format, map, upstream, geo) and
server_blocks/*.conf loads after (uses those definitions).

This fix is backward compatible as definitional directives don't
depend on server blocks.

Discovered while using the Bitnami nginx Helm chart in production.

Fixes: bitnami/charts#36460

Signed-off-by: Andrea Pilo <apilo@cuebiq.com>
2026-02-12 13:51:07 +01:00
..
prebuildfs
rootfs/opt/bitnami [bitnami/nginx] Fix include order for context.d/http ConfigMaps (#90678) 2026-02-12 13:51:07 +01:00
Dockerfile
docker-compose.yml