You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've aligned our images recently to use UBI9 as a base, rather than using multiple images for builds (e.g. using both registry.access.redhat.com/ubi9/nodejs-20 and registry.access.redhat.com/ubi9/nginx-124:latest.
By not using the nginx image, the permissions for logs, cache and pids are restrictive OOTB after a dnf install of the nginx 1.24 package. This results in an error like this when starting with entrypoint.sh:
/usr/share/nginx/html/entrypoint.sh
nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
2024/11/29 15:22:39 [warn] 12#12: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:5
2024/11/29 15:22:39 [emerg] 12#12: open() "/var/log/nginx/error.log" failed (13: Permission denied)
The text was updated successfully, but these errors were encountered:
We've aligned our images recently to use UBI9 as a base, rather than using multiple images for builds (e.g. using both
registry.access.redhat.com/ubi9/nodejs-20
andregistry.access.redhat.com/ubi9/nginx-124:latest
.By not using the nginx image, the permissions for logs, cache and pids are restrictive OOTB after a dnf install of the nginx 1.24 package. This results in an error like this when starting with
entrypoint.sh
:The text was updated successfully, but these errors were encountered: