Bug 1656759 - Nginx:1.12 image has no stdout logs
Summary: Nginx:1.12 image has no stdout logs
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: rh-nginx112-container
Version: rh-nginx112
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.3
Assignee: Luboš Uhliarik ✈
QA Contact: BaseOS QE - Apps
Depends On:
TreeView+ depends on / blocked
Reported: 2018-12-06 09:33 UTC by Abhishek
Modified: 2021-01-14 09:19 UTC (History)
9 users (show)

Fixed In Version: rh-nginx112-container-1-45
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-04-29 10:51:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0893 0 None None None 2019-04-25 17:21:57 UTC

Description Abhishek 2018-12-06 09:33:42 UTC
Description of problem: Nginx:1.12 image build on rhel base image is not showing stdout logs output.

How reproducible:

Steps to Reproduce:
1. oc new-app --template=nginx-example
2. oc logs <nginx-pod-name>

Actual results:

Expected results:
It should show nginx log:
Like nginx server is running on a particular port

Additional info:
For rhel image there is no soft link created to redirect the access.log file content from inside the container to stdout
Difference between centos and rhel base nginx image


Above 2 lines are not in rhel base nginx image

Comment 1 K Chandra Sekar 2018-12-20 04:41:21 UTC
Any updates on this one?

Comment 9 Joe Orton 2019-03-18 14:44:39 UTC
Thanks for the report.  We're working on updating the image to fix this.


Comment 10 Joe Orton 2019-03-19 13:00:55 UTC
This is now fixed for the next update to the containers.  By default the nginx images will produce access logs on stdout and error logs on stderr, both of which should be available via "oc logs".  Alternatively, if the NGINX_LOG_TO_VOLUME environment variable is set when running the container, the logs are available at /var/log/nginx/access.log and /var/log/nginx/error.log inside the filesystem.

Comment 18 errata-xmlrpc 2019-04-25 17:21:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.