Nginx won't start, resolvers.conf is missing

Hi,
so i'm testing this chown performance issue npm has when running on my truenas server. Im using latest version so I tried to customize docker image by skipping setting /opt/certbot completely when ran as root (0). I basically just added

if [ "$PUID" = "0" ]; then
log_info "Skipping certbot ownership adjustments because PUID is 0 (root)"
exit 0
fi

before the last block thats supposed to set owner of /opt/certbot folders and it is indeed skipped as intended. My custom image now looks like

FROM jc21/nginx-proxy-manager:2.12.4
COPY 30-ownership.sh /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh
RUN chmod +x /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh

However, after the skip of this chown block, my nginx won't start. I don't see how it would be connected to changes in 30-ownership.sh script, so I assume it is present in original 2.12.4 image as well, but i can't test it without creating customized image because i won't get through that chown block on my truenas server.

❯ Starting nginx ... nginx: [emerg] open() "/etc/nginx/conf.d/include/resolvers.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:5

Start by inspecting /etc/nginx/nginx.conf and the customized 30-ownership.sh in the 2.12.4 image, then reproduce the startup logs to determine why /etc/nginx/conf.d/include/resolvers.conf is absent. Done means the container starts nginx successfully with that include available, without breaking the reported root-user ownership workaround.